Mailing-List: contact issues-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Date: Fri, 28 Feb 2014 22:32:19 +0000 (UTC)
From: "Bill Farner (JIRA)" <jira@apache.org>
To: issues@aurora.incubator.apache.org
Message-ID: <JIRA.12698034.1393624588895.128113.1393626739156@arcas>
In-Reply-To: <JIRA.12698034.1393624588895@arcas>
References: <JIRA.12698034.1393624588895@arcas>
Subject: [jira] [Commented] (AURORA-243) mesos-log should be auto
 initialized
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bill Farner commented on AURORA-243:
------------------------------------

This was actually a deliberate design that we had input on.  The motivation being that in a production setting, it's extremely dangerous for the log to determine that it is empty.  I suggest our provisioning scripts run the above command.

> 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.1.5#6160)