You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Marco Massenzio <m....@gmail.com> on 2016/05/01 06:12:52 UTC
Re: [Breaking Change, MESOS-1865] Redirect to the leader master when
current master is not a leader
@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 <ha...@gmail.com> 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
>
Re: [Breaking Change, MESOS-1865] Redirect to the leader master when
current master is not a leader
Posted by haosdent <ha...@gmail.com>.
Thank you for popup this, have already mark it resolved.
On Mon, May 2, 2016 at 4:32 AM, Marco Massenzio <m....@gmail.com>
wrote:
> Hi,
>
> sorry, I have not kept up with all the new endpoints :)
> If there is already an endpoint (/redirect ?) that essentially addresses
> the issue raised by MESOS-3841
> (https://issues.apache.org/jira/browse/MESOS-3841) then I'd suggest to
> close it and add a note.
>
> (I just saw it and thought it would have been useful, and fun to fix).
>
> --
> *Marco Massenzio*
> http://codetrips.com
>
> On Sat, Apr 30, 2016 at 9:24 PM, haosdent <ha...@gmail.com> wrote:
>
>> Oh, @Marco. Thank you very much for your reply, vinodkone shepherd this
>> and it have already submitted after other kindly guys reviews.
>>
>> For MESOS-3841, it should be resolved now because could get the leading
>> master by "/redirect" endpoint. Do you have any concerns about it? I would
>> like to solve your concerns.
>>
>> On Sun, May 1, 2016 at 12:12 PM, Marco Massenzio <m....@gmail.com>
>> wrote:
>>
>>> @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 <ha...@gmail.com> 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
>>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
>
>
--
Best Regards,
Haosdent Huang
Re: [Breaking Change, MESOS-1865] Redirect to the leader master when
current master is not a leader
Posted by Marco Massenzio <m....@gmail.com>.
Hi,
sorry, I have not kept up with all the new endpoints :)
If there is already an endpoint (/redirect ?) that essentially addresses
the issue raised by MESOS-3841
(https://issues.apache.org/jira/browse/MESOS-3841) then I'd suggest to
close it and add a note.
(I just saw it and thought it would have been useful, and fun to fix).
--
*Marco Massenzio*
http://codetrips.com
On Sat, Apr 30, 2016 at 9:24 PM, haosdent <ha...@gmail.com> wrote:
> Oh, @Marco. Thank you very much for your reply, vinodkone shepherd this
> and it have already submitted after other kindly guys reviews.
>
> For MESOS-3841, it should be resolved now because could get the leading
> master by "/redirect" endpoint. Do you have any concerns about it? I would
> like to solve your concerns.
>
> On Sun, May 1, 2016 at 12:12 PM, Marco Massenzio <m....@gmail.com>
> wrote:
>
>> @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 <ha...@gmail.com> 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
>>>
>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>
Re: [Breaking Change, MESOS-1865] Redirect to the leader master when
current master is not a leader
Posted by Marco Massenzio <m....@gmail.com>.
Hi,
sorry, I have not kept up with all the new endpoints :)
If there is already an endpoint (/redirect ?) that essentially addresses
the issue raised by MESOS-3841
(https://issues.apache.org/jira/browse/MESOS-3841) then I'd suggest to
close it and add a note.
(I just saw it and thought it would have been useful, and fun to fix).
--
*Marco Massenzio*
http://codetrips.com
On Sat, Apr 30, 2016 at 9:24 PM, haosdent <ha...@gmail.com> wrote:
> Oh, @Marco. Thank you very much for your reply, vinodkone shepherd this
> and it have already submitted after other kindly guys reviews.
>
> For MESOS-3841, it should be resolved now because could get the leading
> master by "/redirect" endpoint. Do you have any concerns about it? I would
> like to solve your concerns.
>
> On Sun, May 1, 2016 at 12:12 PM, Marco Massenzio <m....@gmail.com>
> wrote:
>
>> @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 <ha...@gmail.com> 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
>>>
>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>
Re: [Breaking Change, MESOS-1865] Redirect to the leader master when
current master is not a leader
Posted by haosdent <ha...@gmail.com>.
Oh, @Marco. Thank you very much for your reply, vinodkone shepherd this and
it have already submitted after other kindly guys reviews.
For MESOS-3841, it should be resolved now because could get the leading
master by "/redirect" endpoint. Do you have any concerns about it? I would
like to solve your concerns.
On Sun, May 1, 2016 at 12:12 PM, Marco Massenzio <m....@gmail.com>
wrote:
> @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 <ha...@gmail.com> 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
>>
>
>
--
Best Regards,
Haosdent Huang
Re: [Breaking Change, MESOS-1865] Redirect to the leader master when
current master is not a leader
Posted by haosdent <ha...@gmail.com>.
Oh, @Marco. Thank you very much for your reply, vinodkone shepherd this and
it have already submitted after other kindly guys reviews.
For MESOS-3841, it should be resolved now because could get the leading
master by "/redirect" endpoint. Do you have any concerns about it? I would
like to solve your concerns.
On Sun, May 1, 2016 at 12:12 PM, Marco Massenzio <m....@gmail.com>
wrote:
> @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 <ha...@gmail.com> 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
>>
>
>
--
Best Regards,
Haosdent Huang