[jira] [Comment Edited] (MESOS-496) Refactor the MasterDetector (with 'bool contend' option) into new MasterDetector and MasterContender.

["Yan Xu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729667#comment-13729667 ] 

Yan Xu edited comment on MESOS-496 at 11/6/13 12:14 AM:
--------------------------------------------------------

Reviews:
https://reviews.apache.org/r/15221/
https://reviews.apache.org/r/15016/
https://reviews.apache.org/r/13086/
https://reviews.apache.org/r/13087/


was (Author: xujyan):
Reviews:
https://reviews.apache.org/r/14457/
https://reviews.apache.org/r/15016/
https://reviews.apache.org/r/13086/
https://reviews.apache.org/r/13087/

> Refactor the MasterDetector (with 'bool contend' option) into new MasterDetector and MasterContender.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-496
>                 URL: https://issues.apache.org/jira/browse/MESOS-496
>             Project: Mesos
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: 0.14.0
>            Reporter: Yan Xu
>            Assignee: Yan Xu
>
> The MasterDetector code still uses old Zookeeper abstractions and it's error-prone for maintenance and further development. 
> There exists newer and higher-level zookeeper group management abstractions such as zookeeper::Group. After this refactoring Mesos master detecting and contending logic should reside in separate classes which depend on general Zookeeper group leader detection and contention abstractions with Future-pattern APIs. Masters should then use the MasterContender while Slaves and Schedulers should use the MasterDetector.



--
This message was sent by Atlassian JIRA
(v6.1#6144)