-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/46473/#review130008
-----------------------------------------------------------




docs/high-availability.md (line 29)
<https://reviews.apache.org/r/46473/#comment193610>

    Rephrase
    
    "In addition to ZooKeeper, one can get the location of the leading master 
by sending an HTTP request to `/redirect` endpoint on any master."
    
    Kill the second line.



docs/operational-guide.md (line 68)
<https://reviews.apache.org/r/46473/#comment193615>

    ## HTTP requests to non-leading master
    
    HTTP requests to some master endpoints (e.g., /state, /metrics/snapshot) 
can only be answered by the leading master. Such requests made to a non-leading 
master will result in either a `307 Temporary Redirect` (with the location of 
the leading master) or `503 Service Unavailable` (if the master does not know 
who the current leader is).


- Vinod Kone


On April 21, 2016, 4:10 a.m., haosdent huang wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/46473/
> -----------------------------------------------------------
> 
> (Updated April 21, 2016, 4:10 a.m.)
> 
> 
> Review request for mesos, Adam B, Anand Mazumdar, Cody Maloney, Ian Downes, 
> Neil Conway, and Vinod Kone.
> 
> 
> Bugs: MESOS-1865
>     https://issues.apache.org/jira/browse/MESOS-1865
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> In this changes, we update the `high-availability` and
> `operational-guide` documents about master http endpoints redirction
> when current master is not the leader.
> 
> 
> Diffs
> -----
> 
>   docs/high-availability.md b0e744e62081b56e2a24ef5f7304f424424fa3cc 
>   docs/operational-guide.md 5ae7ede3f500380a78364d5c3da2c4cea75e04c5 
> 
> Diff: https://reviews.apache.org/r/46473/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> haosdent huang
> 
>

Reply via email to