Affects Version/s: None
Fix Version/s: None
I have a mesos+marathon cluster of 3 nodes, and /v2/* is always empty/blank on 2 of the 3.
If I bounce the service on the working node then one of the previously blank nodes starts returning data (and the bounced node returns blank api responses when it comes back online).
I am running v0.8.2. I also tested with the latest master (0.9.x) and [surprisingly] got the same result.
I just rebuilt the entire cluster from scratch and everything went smooth and squeaky clean, yet I am still hitting this issue.
Do you have any suggestions or recommendations re: how to triage this?
I sure wish there was a basic marathon.log file in /var/log on each of the servers! (like mesos)