Hi Aaron
Removing NodeInfo did do the trick, thanks. I see the ticket is already
resolved, good news.
Thanks for the help.
On Fri, Sep 7, 2012 at 12:26 AM, aaron morton wrote:
> This is a problem…
>
> [default@system] list NodeIdInfo ;
>> Using default limit of 100
>> ...
>>
>>
This is a problem…
> [default@system] list NodeIdInfo ;
> Using default limit of 100
> ...
> ---
> RowKey: 43757272656e744c6f63616c
> => (column=01efa5d0-e133-11e1--51be601cd0ff, value=0a1020d2,
> timestamp=1344414498989)
> => (column=92109b80-ea0a-11e1--51be601cd0af, valu
forgot to answer your first question. I see this:
INFO 14:31:31,896 No saved local node id, using newly generated:
92109b80-ea0a-11e1--51be601cd0af
On Wed, Sep 5, 2012 at 8:41 AM, Thomas van Neerijnen
wrote:
> Thanks for the help Aaron.
> I've checked NodeIdInfo and LocationInfo as below.
>
Thanks for the help Aaron.
I've checked NodeIdInfo and LocationInfo as below.
What am I looking at? I'm guessing the first row in NodeIdInfo represents
the ring with the node ids, but the second row perhaps dead nodes with old
schemas? That's a total guess, I'd be very interested to know what it an
Hmmm, this looks like an error in ctor for NodeId$LocalNodeIdHistory. Are there
any other ERROR log messages?
Do you see either of these two messages in the log:
"No saved local node id, using newly generated: {}"
or
"Saved local node id: {}"
Can you use cassandra-cli / cqlsh to print the conte
Hi
I have a single node in a 6 node Cassandra 1.0.11 cluster that seems to
have a single column family in a weird state.
Repairs, upgradesstables, anything that touches this CF crashes.
I've drained the node, removed every file for this CF from said node,
removed the commit log, started it up and
