Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 59810 invoked from network); 5 Aug 2010 09:11:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Aug 2010 09:11:22 -0000 Received: (qmail 88402 invoked by uid 500); 5 Aug 2010 09:11:21 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 88100 invoked by uid 500); 5 Aug 2010 09:11:18 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 88092 invoked by uid 99); 5 Aug 2010 09:11:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Aug 2010 09:11:17 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.216.172] (HELO mail-qy0-f172.google.com) (209.85.216.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Aug 2010 09:11:09 +0000 Received: by qyk1 with SMTP id 1so2828755qyk.10 for ; Thu, 05 Aug 2010 02:10:47 -0700 (PDT) Received: by 10.224.45.134 with SMTP id e6mr4670741qaf.317.1280999447223; Thu, 05 Aug 2010 02:10:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.186.145 with HTTP; Thu, 5 Aug 2010 02:10:27 -0700 (PDT) From: =?UTF-8?Q?Utku_Can_Top=C3=A7u?= Date: Thu, 5 Aug 2010 11:10:27 +0200 Message-ID: Subject: Having different 0.6.x instances in one Cassandra cluster To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0015175ce032026008048d0fed3d X-Virus-Checked: Checked by ClamAV on apache.org --0015175ce032026008048d0fed3d Content-Type: text/plain; charset=UTF-8 Hi All, I'm planning to use the current 0.6.4 stable for creating an image that would be the base for nodes in our Cassandra cluster. However, the 0.6.5 release is on the way. When the 0.6.5 has been released. Is it possible to have some of the nodes stay in 0.6.4 and having new nodes in 0.6.5? Best Regards, Utku --0015175ce032026008048d0fed3d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi All,

I'm planning to use the current 0.6.4 stable for creatin= g an image that would be the base for nodes in our Cassandra cluster.
However, the 0.6.5 release is on the way. When the 0.6.5 has been release= d. Is it possible to have some of the nodes stay in 0.6.4 and having new no= des in 0.6.5?

Best Regards,

Utku
--0015175ce032026008048d0fed3d--