[
https://issues.apache.org/jira/browse/AURORA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174011#comment-14174011
]
Jie Yu commented on AURORA-243:
-------------------------------
[~jaybuff] mesos-log initialize should only be used when the operator sets up a
new cluster (when all replicas are empty). It's a serious error to call the
command while some other replicas are not empty.
Consider this scenario: schedulers are running on hosts A, B, C. Hosts B and C
go down and their disks are replaced. When the operator restart schedulers on
hosts B and C with empty replica, he should not use 'mesos-log initialize'.
Otherwise, B and C can assemble a quorum and effectively erase everything in
the database.
> 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
> 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)
