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 static.void.dev@gmail.com
 designates 209.85.210.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=QmBWXLpKc6m4p2ZF6Yu3DTU1iiWfGmvbYvdztStLPbPcicKnXORgzgQW0AhBadC7Wr
         sR72wQAJ9Bf4sKA+1/OiZY3PMNLp2moG4oe2DnjPJEMyxglf5HJ05aRl3GhBZSQIHs2u
         6B1lP1VekkFHVzJfDZth1Bcu2aa3trnsLgd0Q=
Message-ID: <4C76EDFF.8070207@gmail.com>
Date: Thu, 26 Aug 2010 15:43:11 -0700
From: Mark <static.void.dev@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Repair help
References: <e9579b43-f81c-6695-e0be-bdd52c59e1c3@me.com>
In-Reply-To: <e9579b43-f81c-6695-e0be-bdd52c59e1c3@me.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

  On 8/26/10 3:03 PM, Aaron Morton wrote:
> Check the logs for errors and run nodetool streams to see if it's 
> moving data around.
>
> Aaron
>
>
> On 27 Aug, 2010,at 09:53 AM, Mark <static.void.dev@gmail.com> wrote:
>
>> I have a 2 node cluster (testing the waters) w/ a replication factor
>> of 2. One node got completed screwed up (see any of my previous messages
>> from today) so I deleted the commit log and data directory. I restarted
>> the node and rain nodetool repair as describe in
>> http://wiki.apache.org/cassandra/Operations. I waited for over an hour
>> and checked my ring only to find that nothing was repaired/replicated???
>> I only have a mere 7gigs of data so I would have thought this would have
>> been fairly quick?
>>
>> Address Status State Load Token
>>
>> 129447565151094499156612104441060791022
>> x.x.x.x Up Normal 7.31 GB
>> 12949228055906550350782255148181029323
>> x.x.x.x Up Normal 30.01 MB
>> 129447565151094499156612104441060791022
>>
>> I tried the alternative method of manually removing the token and then
>> bootstrapping however when I tried to remove the token via nodetool
>> removetoken an IllegalStateException was thrown... "replication factor
>> (2) exceeds number of endpoints (1)"
>>
>> What should I do in this situation to get my node back up to where it
>> should be? Is there anywhere I can check that the repair is actually
>> running?
>>
>> Thanks for any suggestions
>>
>> ps I'm using 0.7.0 beta 1
>>
>>
>>
Nothing in the logs (log level is set to ERROR though)

Streams:

bin/nodetool --host localhost --port 8080 streams
Mode: Normal
Not sending any streams.
Not receiving any streams.

Any reason in jconsole the forceTableFlush and forceTableRepair are 
grayed out?