Oh shoot, this is a seed node. Is there documentation on how to bootstrap a seed node? If I have seeds of A, B, C for every machine on the ring and I am bootstrapping node B, do I just modify cassandra.yaml and remove node B from the yaml file temporarily and boot it up (Note, I still received the unknown keyspace errors :( but it is bootstrapping now) and I assume I can add node B back once all the data is in there.
Thanks, Dean On 6/24/13 6:55 AM, "Hiller, Dean" <dean.hil...@nrel.gov> wrote: >Ah, so digging deeper, it is not bootstrapping. How do I force the node >to bootstrap? (this is version 1.2.2 and the other nodes somehow knew to >bootstrap automatically but this one I need to force for some reason). I >remember there was a property for this. > >NOTE: I enabled some debug logs and auto bootstrap is true according to >this log >DEBUG 06:53:03,411 setting auto_bootstrap to true > >OR better yet, if someone can point me to the code on where bootstrap is >decided so I can see why it decides not to bootstrap? > >Thanks, >Dean > >On 6/24/13 6:42 AM, "Hiller, Dean" <dean.hil...@nrel.gov> wrote: > >>I haven't seen this error in a long time. We just received the below >>error in production when rebuilding a nodeŠany ideas on how to get around >>this? We had rebuilt 3 other nodes already I think(we have been swapping >>hardware) >> >>ERROR 06:32:21,474 Exception in thread Thread[ReadStage:1,5,main] >>java.lang.AssertionError: Unknown keyspace databus5 >>at org.apache.cassandra.db.Table.<init>(Table.java:263) >>at org.apache.cassandra.db.Table.open(Table.java:110) >>at org.apache.cassandra.db.Table.open(Table.java:88) >>at >>org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47) >>at >>org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java >>: >>56) >>at >>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor >>. >>java:895) >>at >>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.jav >>a >>:918) >>at java.lang.Thread.run(Thread.java:662) >> >>Thanks for any insight, >>Dean >
