[jira] [Commented] (MESOS-5828) Modularize Network in replicated_log

2019-04-22 Thread longfei (JIRA)


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

longfei commented on MESOS-5828:


Actually, I have made some modifications to MESOS-1806(based on Jay Guo's 
work), and it(etcd contender/detector) works fine for my test mesos cluster. 

I'll commit a patch if needed.

 

The problem is that Replicated Log only works when ZK is present. I think some 
abstraction would make it more flexible and elegant.

Anyway, I'll try zetcd. Thanks a lot!

> Modularize Network in replicated_log
> 
>
> Key: MESOS-5828
> URL: https://issues.apache.org/jira/browse/MESOS-5828
> Project: Mesos
>  Issue Type: Bug
>  Components: replicated log
>Reporter: Jay Guo
>Assignee: Jay Guo
>Priority: Major
>
> Currently replicated_log relies on Zookeeper for coordinator election. This 
> is done through network abstraction _ZookeeperNetwork_. We need to modularize 
> this part in order to enable replicated_log when using Master 
> contender/detector modules.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MESOS-5828) Modularize Network in replicated_log

2019-04-22 Thread Joseph Wu (JIRA)


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

Joseph Wu commented on MESOS-5828:
--

Progress on this has been paused for a while (although the bulk of the patches 
are still usable).

In the meantime, you can try using zetcd, which basically exposes a ZK API for 
etcd:
https://github.com/etcd-io/zetcd

See this thread too: 
https://issues.apache.org/jira/browse/MESOS-1806?focusedCommentId=15895593&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-15895593

> Modularize Network in replicated_log
> 
>
> Key: MESOS-5828
> URL: https://issues.apache.org/jira/browse/MESOS-5828
> Project: Mesos
>  Issue Type: Bug
>  Components: replicated log
>Reporter: Jay Guo
>Assignee: Jay Guo
>Priority: Major
>
> Currently replicated_log relies on Zookeeper for coordinator election. This 
> is done through network abstraction _ZookeeperNetwork_. We need to modularize 
> this part in order to enable replicated_log when using Master 
> contender/detector modules.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MESOS-5828) Modularize Network in replicated_log

2019-04-19 Thread longfei (JIRA)


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

longfei commented on MESOS-5828:


Hi [~kaysoky]. Is this patching still in progress or stopped? 

I want to use etcd instead of ZK in some edge environments because ZK uses to 
much resource and is too complicated as a coordinator.

> Modularize Network in replicated_log
> 
>
> Key: MESOS-5828
> URL: https://issues.apache.org/jira/browse/MESOS-5828
> Project: Mesos
>  Issue Type: Bug
>  Components: replicated log
>Reporter: Jay Guo
>Assignee: Jay Guo
>Priority: Major
>
> Currently replicated_log relies on Zookeeper for coordinator election. This 
> is done through network abstraction _ZookeeperNetwork_. We need to modularize 
> this part in order to enable replicated_log when using Master 
> contender/detector modules.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MESOS-5828) Modularize Network in replicated_log

2016-08-05 Thread Jay Guo (JIRA)

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

Jay Guo commented on MESOS-5828:


Updated patch chain summary:

||Reviews||Summary||
|https://reviews.apache.org/r/50837|Fixed minor code style.|
|https://reviews.apache.org/r/50491|Added PIDGroup to libprocess.|
|https://reviews.apache.org/r/50492|Switched replicated log to use PIDGroup.|
|https://reviews.apache.org/r/50490|Separated ZooKeeper PIDGroup implementation 
into its own cpp/hpp.|
|https://reviews.apache.org/r/50493|Added `base` to PIDGroup.|
|https://reviews.apache.org/r/50494|Remove `base` from ZooKeeperPIDGroup.|
|https://reviews.apache.org/r/50495|Added PIDGroup module struct.|
|https://reviews.apache.org/r/50496|Added static `createPIDGroup` method to 
LogProcess.|
|https://reviews.apache.org/r/50497|Added new constructors in Log and 
LogProcess.|
|https://reviews.apache.org/r/50498|Added --pid_group flag in master.|
|https://reviews.apache.org/r/50499|Added logic in master/main.cpp to use 
pid_group module.|
|https://reviews.apache.org/r/50838|Updated modules documentation to reflect 
PIDGroup module.|

> Modularize Network in replicated_log
> 
>
> Key: MESOS-5828
> URL: https://issues.apache.org/jira/browse/MESOS-5828
> Project: Mesos
>  Issue Type: Bug
>  Components: replicated log
>Reporter: Jay Guo
>Assignee: Jay Guo
>
> Currently replicated_log relies on Zookeeper for coordinator election. This 
> is done through network abstraction _ZookeeperNetwork_. We need to modularize 
> this part in order to enable replicated_log when using Master 
> contender/detector modules.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)