From user-return-38813-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Wed Feb 5 19:25:21 2014 Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DCD95100C9 for ; Wed, 5 Feb 2014 19:25:21 +0000 (UTC) Received: (qmail 46622 invoked by uid 500); 5 Feb 2014 19:24:10 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 45822 invoked by uid 500); 5 Feb 2014 19:23:52 -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 45600 invoked by uid 99); 5 Feb 2014 19:23:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Feb 2014 19:23:48 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kwright@nanigans.com designates 216.82.251.14 as permitted sender) Received: from [216.82.251.14] (HELO mail1.bemta12.messagelabs.com) (216.82.251.14) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Feb 2014 19:23:44 +0000 Received: from [216.82.250.115:8847] by server-14.bemta-12.messagelabs.com id 39/37-27892-BAF82F25; Wed, 05 Feb 2014 19:23:23 +0000 X-Env-Sender: kwright@nanigans.com X-Msg-Ref: server-11.tower-127.messagelabs.com!1391628196!5697618!13 X-Originating-IP: [216.166.12.180] X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29797 invoked from network); 5 Feb 2014 19:23:22 -0000 Received: from out001.collaborationhost.net (HELO out001.collaborationhost.net) (216.166.12.180) by server-11.tower-127.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 19:23:22 -0000 Received: from AUSP01VMBX28.collaborationhost.net ([192.168.20.73]) by AUSP01MHUB05.collaborationhost.net ([10.2.8.172]) with mapi; Wed, 5 Feb 2014 13:23:32 -0600 From: Keith Wright To: "user@cassandra.apache.org" CC: Don Jackson , Dave Carroll Date: Wed, 5 Feb 2014 13:22:23 -0600 Subject: Re: Move to smaller nodes Thread-Topic: Move to smaller nodes Thread-Index: Ac8ip8HI9tupWJXLSs2W4c1uZGix/A== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.3.120616 acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_CF17F9771F73Ckwrightnaniganscom_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_CF17F9771F73Ckwrightnaniganscom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Also there is one more option which is we could upgrade to 2.0 in the hopes= that our issue is fixed as part of the streaming overhaul. But seeing as = this is a production cluster and 2.0 does not yet appear production ready, = that makes me nervous. From: Keith Wright > Reply-To: "user@cassandra.apache.org" > Date: Wednesday, February 5, 2014 at 2:18 PM To: "user@cassandra.apache.org" > Cc: Don Jackson >, Dave= Carroll > Subject: Re: Move to smaller nodes Hi Rob, thanks for the response! Interestingly if we run a repair we don= =92t see the bootstrap issue so I am considering doing the empty node repai= r methodology. Its just that it usually takes a week for that to work. As= I see it, we could try the following to fix the bootstrap issue: * Update our JRE, we are using 1.7.0_17 and I believe we=92re up to 1.7.= 0_54 * GC tuning as it does appear that we=92re suffering from GC issues. We= could just allocate more eden space and then revert after the bootstrap su= cceeds * As I mentioned, don=92t load data via bootstrap but instead use repair= . With bootstrap disabled in Vnodes, will the node still assign itself tok= ens? Thanks From: Robert Coli > Reply-To: "user@cassandra.apache.org" > Date: Wednesday, February 5, 2014 at 2:10 PM To: "user@cassandra.apache.org" > Cc: Don Jackson >, Dave= Carroll > Subject: Re: Move to smaller nodes http://www.palominodb.com/blog/2012/09/25/bulk-loading-options-cassandra --_000_CF17F9771F73Ckwrightnaniganscom_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Also there is one more option wh= ich is we could upgrade to 2.0 in the hopes that our issue is fixed as part= of the streaming overhaul.  But seeing as this is a production cluste= r and 2.0 does not yet appear production ready, that makes me nervous.

From: Keith W= right <kwright@nanigans.com&= gt;
Reply-To: "user@cassandra.apache.org" <<= a href=3D"mailto:user@cassandra.apache.org">user@cassandra.apache.org&g= t;
Date: Wednesday, February 5,= 2014 at 2:18 PM
To: "user@cassandra.apache.org"= ; <user@cassandra.apache.or= g>
Cc: Don Jackson <<= a href=3D"mailto:djackson@nanigans.com">djackson@nanigans.com>, Dave= Carroll <dcarroll@nanigans.com= >
Subject: Re: Move to s= maller nodes

Hi = Rob, thanks for the response!  Interestingly if we run a repair we don= =92t see the bootstrap issue so I am considering doing the empty node repai= r methodology.  Its just that it usually takes a week for that to work= .  As I see it, we could try the following to fix the bootstrap issue:
--_000_CF17F9771F73Ckwrightnaniganscom_--