Re: Lost data after expanding cluster c* 1.2.3-1

Sorry can you repost the details of that issue including the CL you are using. Aaron - Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 17/04/2013, at 12:57 AM, Kais Ahmed wrote: > Thanks aaron, > > I feel that rebuilding i

Re: Lost data after expanding cluster c* 1.2.3-1

Thanks aaron, I feel that rebuilding indexes went well, but the result of my query (SELECT * FROM userdata WHERE login='kais';) is still emty. INFO [Creating index: userdata.userdata_login_idx] 2013-03-30 01:16:33,110 SecondaryIndex.java (line 175) Submitting index build of userdata.userdata_logi

Re: Lost data after expanding cluster c* 1.2.3-1

Look in the logs for messages from the SecondaryIndexManager starts with "Submitting index build of" end with "Index build of" Cheers - Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 7/04/2013, at 12:55 AM, Kais Ahmed wrot

Re: Lost data after expanding cluster c* 1.2.3-1

hi aaron, nodetool compactionstats on all nodes return 1 pending task : ubuntu@app:~$ nodetool compactionstats host pending tasks: 1 Active compaction remaining time :n/a The command nodetool rebuild_index was launched several days ago. 2013/4/5 aaron morton > but nothing's happening,

Re: Lost data after expanding cluster c* 1.2.3-1

> but nothing's happening, how can i monitor the progress? and how can i know > when it's finished? check nodetool compacitonstats Cheers - Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 4/04/2013, at 2:51 PM, Kais Ahmed w

Re: Lost data after expanding cluster c* 1.2.3-1

Hi aaron, I ran the command "nodetool rebuild_index host keyspace cf" on all the nodes, in the log i see : INFO [RMI TCP Connection(5422)-10.34.139.xxx] 2013-04-04 08:31:53,641 ColumnFamilyStore.java (line 558) User Requested secondary index re-build for ... but nothing's happening, how can i mo

Re: Lost data after expanding cluster c* 1.2.3-1

> The problem come from that i don't put auto_boostrap to true for the new > nodes, not in this documentation > (http://www.datastax.com/docs/1.2/install/expand_ami) auto_bootstrap defaults to True if not specified in the yaml. > can i do that at any time, or when the cluster are not loaded No

Re: Lost data after expanding cluster c* 1.2.3-1

> At this moment the errors started, we see that members and other data are gone, at this moment the nodetool status return (in red color the 3 new nodes) > What errors? The errors was in my side in the application, not cassandra errors > I put for each of them seeds = A ip, and start each with tw

Re: Lost data after expanding cluster c* 1.2.3-1

Please do not rely on colour in your emails, the best way to get your emails accepted by the Apache mail servers is to use plain text. > At this moment the errors started, we see that members and other data are > gone, at this moment the nodetool status return (in red color the 3 new nodes) Wha

Re: Lost data after expanding cluster c* 1.2.3-1

Hi aaron, Thanks for reply, i will try to explain what append exactly I had 4 C* called [A,B,C,D] cluster (1.2.3-1 version) start with ec2 ami ( https://aws.amazon.com/amis/datastax-auto-clustering-ami-2-2) with this config --clustername myDSCcluster --totalnodes 4--version community Two days af

Re: Lost data after expanding cluster c* 1.2.3-1

First thought is the new nodes were marked as seeds. Next thought is check the logs for errors. You can always run a nodetool repair if you are concerned data is not where you think it should be. Cheers - Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton

Lost data after expanding cluster c* 1.2.3-1

Hi all, I follow this tutorial for expanding a 4 c* cluster (production) and add 3 new nodes. Datacenter: eu-west === Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens Owns Host ID Rack UN 10.34.142.xxx