Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of nick@datastax.com designates
 209.85.214.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAF+j8ak-NC+mCoGuOPh4J_rm3jx-hy2F_FOubY_UGK28GZUa3w@mail.gmail.com>
References: 
 <CAF+j8aky7LATo0hH-EQPoNH4tXXv0Z32ZAPq1RceZFpnFSfF9g@mail.gmail.com>
 <CALHkrw8i_F__B7jqNCjMWJkZ40A0xXwLRQqN2Aq+HhWySZqSug@mail.gmail.com>
 <CAF+j8an5dojrBfODiv6CroBr=QLPZVUseeUKWjJPG_N3849gCw@mail.gmail.com>
 <CALHkrw8w+mTpSMyyaE0XX6PUOmeYo9_yROzYB4uRtgj8B28M0Q@mail.gmail.com>
 <CAF+j8an+pybCAtmDUQQmg=HKpxpJGyfzBT1gZvUxjTxVvsei7Q@mail.gmail.com>
 <CAF+j8anZD7r46DZwDOKUUDP57w=0nfavmormEQcag0Krsx5L6Q@mail.gmail.com>
 <E9038335-6629-4173-918D-ECD298F2D4A6@thelastpickle.com>
 <CAF+j8ak-NC+mCoGuOPh4J_rm3jx-hy2F_FOubY_UGK28GZUa3w@mail.gmail.com>
From: Nick Bailey <nick@datastax.com>
Date: Tue, 19 Jun 2012 23:32:37 -0500
Message-ID: 
 <CALHkrw_d-NK2jGxNoPne5Xr5uOwnpfHGzn6LWHsm3Y+76geEUg@mail.gmail.com>
Subject: Re: Unbalanced ring in Cassandra 0.8.4
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

No. Cleanup will scan each sstable to remove data that is no longer
owned by that specific node. It won't compact the sstables together
however.

On Tue, Jun 19, 2012 at 11:11 PM, Raj N <raj.cassandra@gmail.com> wrote:
> But wont that also run a major compaction which is not recommended anymor=
e.
>
> -Raj
>
>
> On Sun, Jun 17, 2012 at 11:58 PM, aaron morton <aaron@thelastpickle.com>
> wrote:
>>
>> Assuming you have been running repair, it' can't hurt.
>>
>> Cheers
>>
>> -----------------
>> Aaron Morton
>> Freelance Developer
>> @aaronmorton
>> http://www.thelastpickle.com
>>
>> On 17/06/2012, at 4:06 AM, Raj N wrote:
>>
>> Nick, do you think I should still run cleanup on the first node.
>>
>> -Rajesh
>>
>> On Fri, Jun 15, 2012 at 3:47 PM, Raj N <raj.cassandra@gmail.com> wrote:
>>>
>>> I did run nodetool move. But that was when I was setting up the cluster
>>> which means I didn't have any data at that time.
>>>
>>> -Raj
>>>
>>>
>>> On Fri, Jun 15, 2012 at 1:29 PM, Nick Bailey <nick@datastax.com> wrote:
>>>>
>>>> Did you start all your nodes at the correct tokens or did you balance
>>>> by moving them? Moving nodes around won't delete unneeded data after
>>>> the move is done.
>>>>
>>>> Try running 'nodetool cleanup' on all of your nodes.
>>>>
>>>> On Fri, Jun 15, 2012 at 12:24 PM, Raj N <raj.cassandra@gmail.com> wrot=
e:
>>>> > Actually I am not worried about the percentage. Its the data I am
>>>> > concerned
>>>> > about. Look at the first node. It has 102.07GB data. And the other
>>>> > nodes
>>>> > have around 60 GB(one has 69, but lets ignore that one). I am not
>>>> > understanding why the first node has almost double the data.
>>>> >
>>>> > Thanks
>>>> > -Raj
>>>> >
>>>> >
>>>> > On Fri, Jun 15, 2012 at 11:06 AM, Nick Bailey <nick@datastax.com>
>>>> > wrote:
>>>> >>
>>>> >> This is just a known problem with the nodetool output and multiple
>>>> >> DCs. Your configuration is correct. The problem with nodetool is
>>>> >> fixed
>>>> >> in 1.1.1
>>>> >>
>>>> >> https://issues.apache.org/jira/browse/CASSANDRA-3412
>>>> >>
>>>> >> On Fri, Jun 15, 2012 at 9:59 AM, Raj N <raj.cassandra@gmail.com>
>>>> >> wrote:
>>>> >> > Hi experts,
>>>> >> > =A0 =A0 I have a 6 node cluster across 2 DCs(DC1:3, DC2:3). I hav=
e
>>>> >> > assigned
>>>> >> > tokens using the first strategy(adding 1) mentioned here -
>>>> >> >
>>>> >> > http://wiki.apache.org/cassandra/Operations?#Token_selection
>>>> >> >
>>>> >> > But when I run nodetool ring on my cluster, this is the result I
>>>> >> > get -
>>>> >> >
>>>> >> > Address =A0 =A0 =A0 =A0 DC =A0Rack =A0Status State =A0 Load =A0 =
=A0 =A0 =A0Owns =A0 =A0Token
>>>> >> >
>>>> >> > =A0113427455640312814857969558651062452225
>>>> >> > 172.17.72.91 =A0 =A0DC1 RAC13 Up =A0 =A0 Normal =A0102.07 GB =A0 =
33.33% =A00
>>>> >> > 45.10.80.144 =A0 =A0DC2 RAC5 =A0Up =A0 =A0 Normal =A059.1 GB =A0 =
=A0 0.00% =A0 1
>>>> >> > 172.17.72.93 =A0 =A0DC1 RAC18 Up =A0 =A0 Normal =A059.57 GB =A0 =
=A033.33%
>>>> >> > =A056713727820156407428984779325531226112
>>>> >> > 45.10.80.146 =A0 =A0DC2 RAC7 =A0Up =A0 =A0 Normal =A059.64 GB =A0=
 =A00.00%
>>>> >> > 56713727820156407428984779325531226113
>>>> >> > 172.17.72.95 =A0 =A0DC1 RAC19 Up =A0 =A0 Normal =A069.58 GB =A0 =
=A033.33%
>>>> >> > =A0113427455640312814857969558651062452224
>>>> >> > 45.10.80.148 =A0 =A0DC2 RAC9 =A0Up =A0 =A0 Normal =A059.31 GB =A0=
 =A00.00%
>>>> >> > 113427455640312814857969558651062452225
>>>> >> >
>>>> >> >
>>>> >> > As you can see the first node has considerably more load than the
>>>> >> > others(almost double)=A0which is surprising since all these are
>>>> >> > replicas
>>>> >> > of
>>>> >> > each other. I am running Cassandra 0.8.4. Is there an explanation
>>>> >> > for
>>>> >> > this
>>>> >> > behaviour?
>>>> >> > Could=A0https://issues.apache.org/jira/browse/CASSANDRA-2433=A0be
>>>> >> > the
>>>> >> > cause for this?
>>>> >> >
>>>> >> > Thanks
>>>> >> > -Raj
>>>> >
>>>> >
>>>
>>>
>>
>>
>