I personally believe that this is not a sufficient workaround -- what if the master is failing over, and your autoscaler happens to redirect to a master which just lost leadership?
This solution is inherently racy and leads to the end user writing extra code to work around it, and even then can still result in extremely difficult to diagnose bugs. I'd filed an issue on this a while ago (0.20 days): https://issues.apache.org/jira/browse/MESOS-1865 but unfortunately it is still not resolved. > On Apr 13, 2016, at 12:44 AM, Alexander Rojas <[email protected]> wrote: > > Hi guillermo, > > The master has the `/redirect` endpoint which should point you to the current > leader. > >> On 13 Apr 2016, at 08:20, Guillermo Rodriguez <[email protected]> wrote: >> >> Hi, >> >> I have 3 mesos master setup for HA. One has the lead. >> >> http://172.31.35.90:5050/master/slaves <<< leader, returns slave list >> http://172.31.35.91:5050/master/slaves <<< follower, returns empty list >> http://172.31.35.92:5050/master/slaves <<< follower, returns empty list >> >> I have an URL mesos-master.mydomain.com pointing to the leader and that >> works fine because it returns the slave list which I need for my autoscaler. >> But I'm afraid if the master fails the URL will no longer be valid. So I >> added the three IPs to the router (AWS Route53) so it would round robin, >> but of course this will return an empty list sometimes because it hits a >> follower which returns empty. >> >> So my question is, is it possible to redirect the call from the followers to >> the leader master? >> >> Thanks. >> >
signature.asc
Description: Message signed with OpenPGP using GPGMail
