Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1467750320.1257449672794.JavaMail.jira@brutus>
Date: Thu, 5 Nov 2009 19:34:32 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Updated: (CASSANDRA-526) Operations: Allow the ability to
 start a node without joining the ring
In-Reply-To: <2072697734.1257353612435.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis updated CASSANDRA-526:
-------------------------------------

        Fix Version/s:     (was: 0.5)
    Affects Version/s:     (was: 0.5)

> Operations: Allow the ability to start a node without joining the ring
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-526
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-526
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Chris Goffinet
>            Priority: Minor
>
> In environments with a dedicated operations team, it might make sense for some organizations to start Cassandra nodes with a flag that allows them to bootup, but not join the ring until they receive an explicit command. This would help in situations if certain actions need to happen from the engineering side before certain nodes go live and take on traffic.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.