@haosdent - thanks for doing this, very useful indeed! On a related issue [0], I'd like to that one on:
- can anyone comment if that's a good idea/bad idea; and - would anyone be willing to shepherd it? Thanks! [0] Master HTTP API support to get the leader ( https://issues.apache.org/jira/browse/MESOS-3841) -- *Marco Massenzio* http://codetrips.com On Tue, Apr 19, 2016 at 12:34 AM, haosdent <[email protected]> wrote: > Hi All, > > We intend to introduce a breaking change[1] in the http endpoints without > the deprecation cycle. > For below http endpoints, when user request to a master which is not a > leader, > user would get a 307 redirect(TEMPORARY_REDIRECT) to the leader master. > > * /create-volumes > * /destroy-volumes > * /frameworks > * /reserve > * /slaves > * /quota > * /weights > * /state > * /state.json > * /state-summary > * /tasks > * /tasks.json > * /roles > * /roles.json > * /teardown > * /maintenance/schedule > * /maintenance/status > * /machine/down > * /machine/up > * /unreserve > > For other endpoints in master, the behaviour is not change. > > If your existing framework/tool relied on the old behaviour, I suggest to > add a logic to handle 307 redirect response. > Please let me know if you have any queries/concerns. Any comments will be > appreciated. > > Links: > [1] Tracking JIRA: https://issues.apache.org/jira/browse/MESOS-1865 > > -- > Best Regards, > Haosdent Huang >
