[
https://issues.apache.org/jira/browse/MYRIAD-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310659#comment-15310659
]
Zachary Jaffee commented on MYRIAD-134:
---------------------------------------
Also, semi-related, we should probably open an epic to introduce better
monitoring which could involve using Consul.
But anyways, as of now since there is already a ZK dependency for Myriad
implementing this makes perfect sense, if anything having the state be stored
in ZK should be a top priority, as if you want to do a zero down time upgrade,
it would be a lot easier to pass the state to the new cluster using ZK than
having to pass the physical file if you want to keep the state between
deployments.
[~darinj] if this ticket isn't being actively worked on I'd be happy to take a
crack at it.
> Support Zookeeper based implementation of RMStateStore for storing Myriad
> state
> -------------------------------------------------------------------------------
>
> Key: MYRIAD-134
> URL: https://issues.apache.org/jira/browse/MYRIAD-134
> Project: Myriad
> Issue Type: Task
> Components: Scheduler
> Reporter: Swapnil Daingade
> Assignee: Swapnil Daingade
>
> Currently we support a DFS based implementation of RMStateStore for storing
> Myriad State (MyriadFileSystemRMStateStore). We need to similarly support a
> Zookeeper base one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
