aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Brazil (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-243) mesos-log should be auto initialized
Date Wed, 07 Jan 2015 12:23:34 GMT

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

Brian Brazil commented on AURORA-243:
-------------------------------------

One option might be to track whether we've ever initialised the log in zookeeper, as that
can maintain consistent persisted state.

So at startup, if the log's not initialised and a given zookeeper node doesn't exist you'd
initialise the log, and that node. For transition, if the log's initialised you'd create the
zookeeper node if it doesn't exist. If the log's not initialised and the zookeeper node doesn't
exist, do nothing.

This protect against a set of empty nodes appearing in a cluster, while still allowing auto-initilisation
which makes initial cluster setup easier.

> mesos-log should be auto initialized 
> -------------------------------------
>
>                 Key: AURORA-243
>                 URL: https://issues.apache.org/jira/browse/AURORA-243
>             Project: Aurora
>          Issue Type: Story
>          Components: Continuous Integration
>            Reporter: Jake Farrell
>            Priority: Trivial
>              Labels: newbie
>
> The replicated log currently requires the invocation of a manual tool to initialize from
a full set of empty replicas this is seen in examples/vagrant/provision-aurora-scheduler.sh
line 95
> {code}
> mesos-log initialize <path_to_the_log>
> {code}
> Track MESOS-984 and remove this when available 



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

Mime
View raw message