Subject: Re: Errors when decommissioning - 0.7 RC1
Your logs seem to indicate you have some node flapping problems.
The logs complain about nodes *.18 and *.17 going down and immediately
coming back up, even before the decommission. Is that common throughout
your logs? If thats the case I would a
Your logs seem to indicate you have some node flapping problems.
The logs complain about nodes *.18 and *.17 going down and immediately
coming back up, even before the decommission. Is that common throughout
your logs? If thats the case I would attribute seeing *.17 down after the
decommission t
Just realized the ring output is included in the logs for both of those
nodes. Disregard my earlier request :).
On Wed, Dec 15, 2010 at 8:27 AM, Nick Bailey wrote:
> This is rc2 I am assuming?
>
> One thing about remove, the removetoken force command is meant to be run on
> the node that origin
This is rc2 I am assuming?
One thing about remove, the removetoken force command is meant to be run on
the node that originally started a remove and doesn't take a token
parameter. Not relevant to you problem though.
Is this a test cluster and have you tried to reproduce the error? I would be
in
I am seeing very strange things when trying to decommission a node in my
cluster (detailed logs attached). Here is a nodetool ring report *after*
decommissioning of node 192.168.4.19 (as seen by any other, properly
functioning node).
192.168.4.15Up Normal 49.9 GB 25.00%
42535
On Wed, Dec 8, 2010 at 12:09 PM, Ned Wolpert wrote:
> Just a note that the README.txt file doesn't show using the ';' in the
> command.
Fixed in RC2 (pending vote completion right now.)
-Brandon
Just a note that the README.txt file doesn't show using the ';' in the
command.
On Thu, Dec 2, 2010 at 10:46 AM, Yikuo Chan wrote:
> Hi Norman :
>
> it's work and thanks for your help ..
>
> Kevin
>
>
> On Fri, Dec 3, 2010 at 1:43 AM, Norman Maurer wrote:
>
>> You need to terminate the command
tml
> https://issues.apache.org/jira/browse/CASSANDRA-1790
> Aaron
>
> On 08 Dec, 2010,at 10:51 AM, Peter Lin wrote:
>
> I just downloaded the 0.7 RC1 and got an error starting cassandra. I
> have 0.6.x working on my system, so I used the conversion tool to
> convert my storage-conf to ca
Sounds like http://www.mail-archive.com/user@cassandra.apache.org/msg07514.htmlhttps://issues.apache.org/jira/browse/CASSANDRA-1790AaronOn 08 Dec, 2010,at 10:51 AM, Peter Lin wrote:I just downloaded the 0.7 RC1 and got an error starting cassandra. I
have 0.6.x working on my system, so I used the
I just downloaded the 0.7 RC1 and got an error starting cassandra. I
have 0.6.x working on my system, so I used the conversion tool to
convert my storage-conf to cassandra.yaml.
it looks like the conversion tool didn't add entries for commitlog and
saved_caches directory in the configuration
Hi Norman :
it's work and thanks for your help ..
Kevin
On Fri, Dec 3, 2010 at 1:43 AM, Norman Maurer wrote:
> You need to terminate the command with a ";".
>
> Try:
> help;
>
> Bye,
> Norman
>
> 2010/12/2 Yikuo Chan :
> > Hi there ,
> >
> > After install cassandra 0.7rc1 , I get no respond p
You need to terminate the command with a ";".
Try:
help;
Bye,
Norman
2010/12/2 Yikuo Chan :
> Hi there ,
>
> After install cassandra 0.7rc1 , I get no respond problem after execute
> cassandra-cli , please reference below log and help
> me to fix this issue :
>
> [r...@xxx cassandra]# bin/cassan
Hi there ,
After install cassandra 0.7rc1 , I get no respond problem after execute
cassandra-cli , please reference below log and help
me to fix this issue :
[r...@xxx cassandra]# bin/cassandra-cli --host 10.31.23.22
Connected to: "xxx Test Cluster" on 10.31.23.22/9160
Welcome to cassandra CLI.
13 matches
Mail list logo
