Yes, please open a ticket for the assertion error. (Once JIRA is back up...)
On Wed, Aug 25, 2010 at 10:46 PM, Aaron Morton wrote:
> yes, starting the others made things a bit happier.
> Any thoughts on the assertion error that cause the startup to fail ? I've
> seen it a couple of times.
> Seem
yes, starting the others made things a bit happier. Any thoughts on the assertion error that cause the startup to fail ? I've seen it a couple of times. Seems to be from this line in CommitLogHeader.java157: assert clHeader.cfDirtiedAt.size() <= clHeader.cfCount;ThanksAaronOn 26 Aug, 20
the one node you restarted thinks it's the only node in the cluster.
starting the others will fix that.
On Wed, Aug 25, 2010 at 10:10 PM, Aaron Morton wrote:
> 0.7.0-bet1 4 node clustered, i'd managed to get it into some sort of awful
> state (i think by accidently creating to many clients, it wa
0.7.0-bet1 4 node clustered, i'd managed to get it into some sort of awful state (i think by accidently creating to many clients, it was also complaining about running out of file handles). Anyway I killed it all and restarted just one node, thought I would let it settle down then start the others.
