Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 24 May 2011 22:15:47 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1654181274.40862.1306275347888.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <441282713.12171.1300469669587.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CASSANDRA-2356) make the debian package never
 start by default
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams updated CASSANDRA-2356:
----------------------------------------

    Fix Version/s:     (was: 0.8.0)
                   1.0
         Assignee: paul cannon  (was: Brandon Williams)

> make the debian package never start by default
> ----------------------------------------------
>
>                 Key: CASSANDRA-2356
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2356
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Jeremy Hanna
>            Assignee: paul cannon
>            Priority: Minor
>              Labels: debian, packaging
>             Fix For: 1.0
>
>         Attachments: 2356.txt
>
>
> Currently the debian package that installs cassandra starts cassandra by default.  It sounds like that is a standard debian packaging convention.  However, if you want to bootstrap a new node and want to configure it before it creates any sort of state information, it's a pain.  I would think that the common use case would be to have it install all of the init scripts and such but *not* have it start up by default.  That way an admin can configure cassandra with seed, token, host, etc. information and then start it.  That makes it easier to programmatically do this as well - have chef/puppet install cassandra, do some configuration, then do the service start.
> With the current setup, it sounds like cassandra creates state on startup that has to be cleaned before a new configuration can take effect.  So the process of installing turns into:
> * install debian package
> * shutdown cassandra
> * clean out state (data/log dirs)
> * configure cassandra
> * start cassandra
> That seems suboptimal for the default case, especially when trying to automate new nodes being bootstrapped.
> Another case might be when a downed node comes back up and starts by default and tries to claim a token that has already been claimed by another newly bootstrapped node.  Rob is more familiar with that case so I'll let him explain it in the comments.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira