[
https://issues.apache.org/jira/browse/MESOS-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102540#comment-15102540
]
Vinod Kone commented on MESOS-3832:
-----------------------------------
Hey Dario. Totally not the intention to blind side you. I think Anand jumped
the gun because he wanted to get it into the 0.27 release happening next week.
Glad to hear you are still interested in driving this. I will ask Anand to
discard his review. Could you please update your review with the feedback (also
assign the ticket back to you). Would love to get the patch in for 0.27.0!
Thanks for filing the bug and submitting the patch, by the way.
> Scheduler HTTP API does not redirect to leading master
> ------------------------------------------------------
>
> Key: MESOS-3832
> URL: https://issues.apache.org/jira/browse/MESOS-3832
> Project: Mesos
> Issue Type: Bug
> Components: HTTP API
> Affects Versions: 0.24.0, 0.24.1, 0.25.0
> Reporter: Dario Rexin
> Assignee: Vinod Kone
> Labels: newbie
>
> The documentation for the Scheduler HTTP API says:
> {quote}If requests are made to a non-leading master a “HTTP 307 Temporary
> Redirect” will be received with the “Location” header pointing to the leading
> master.{quote}
> While the redirect functionality has been implemented, it was not actually
> used in the handler for the HTTP api.
> A probable fix could be:
> - Check if the current master is the leading master.
> - If not, invoke the existing {{redirect}} method in {{src/master/http.cpp}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
