There should be a line between what is stored in state store and what is stored
in ZK (if it is not a state store), as we would need ot maintain two systems of
record in such a case.
Definitely ZK has such advantages as "triggers" and MyriadScheduler can find
out instantly if something was changed/removed/deleted and in case of multiple
MyriadSchedulers running it would be an advantage. I just don't think we would
have such a situation where we have multiple MyriadSchedulers acting as masters.
and BTW - those comments do not get on the JIRA, so we better continue
conversation on the JIRA.
From: John Omernik <j...@omernik.com>
To: dev@myriad.incubator.apache.org
Sent: Tuesday, September 8, 2015 11:27 AM
Subject: Re: [jira] [Commented] (MYRIAD-129) Creating custom profiles requires
configurations changes on all nodes.
Since the profile information is small, could this be done in Zookeeper?
On Tue, Sep 8, 2015 at 12:59 PM, Yuliya Feldman (JIRA) <j...@apache.org>
wrote:
>
> [
> https://issues.apache.org/jira/browse/MYRIAD-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735288#comment-14735288
> ]
>
> Yuliya Feldman commented on MYRIAD-129:
> ---------------------------------------
>
> I think we should have API/UI to add/remove/modify profiles. Also keep all
> the configuration updates in state store in case of failover
>
> > Creating custom profiles requires configurations changes on all nodes.
> > ----------------------------------------------------------------------
> >
> > Key: MYRIAD-129
> > URL: https://issues.apache.org/jira/browse/MYRIAD-129
> > Project: Myriad
> > Issue Type: Bug
> > Reporter: Aashreya Ravi Shankar
> >
>
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>
