I re-read my response, and in case it was unclear, I meant:
I applied the patch but wasn't able to reuse the old tables. The
patch seems to be working fine after I nuked the data though.
Edmond
On Mon, Oct 19, 2009 at 5:16 PM, Jonathan Ellis jbel...@gmail.com wrote:
Thanks for following up!
Don't know if you tried this yet, but Eric noticed a bug in my patch.
There's a new one now, fixed.
-Jonathan
Jonathan -
I patched in your latest change that dropped the assertions and tried
to restart my cluster on my old data. 2 of 5 nodes still failed to
start, with different errors.
One dies with a generic EOFException during recovery:
INFO - Compacting
Those are both consistent with a different bug that was fixed for
0.4.1 (now released officially!)
-Jonathan
On Fri, Oct 16, 2009 at 4:59 PM, Edmond Lau edm...@ooyala.com wrote:
Jonathan -
I patched in your latest change that dropped the assertions and tried
to restart my cluster on my old
Quicker question: Is this ColumnFamily using UTF8Type as its comparator?
On Thu, Oct 15, 2009 at 1:17 PM, Jonathan Ellis jbel...@gmail.com wrote:
The exception on restart is occurring during a compaction of
already-written sstables. It logs what the files are beforehand
(Compacting [...]).
Yes, I'm using UTF8Type as the comparator.
On Thu, Oct 15, 2009 at 11:33 AM, Jonathan Ellis jbel...@gmail.com wrote:
Quicker question: Is this ColumnFamily using UTF8Type as its comparator?
On Thu, Oct 15, 2009 at 1:17 PM, Jonathan Ellis jbel...@gmail.com wrote:
The exception on restart is
Aha! :)
Could you test the patch attached to
https://issues.apache.org/jira/browse/CASSANDRA-493 ?
(If you're using the binary release, you can get the source from
https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.0-final/
and build with ant)
thanks,
-Jonathan
On Thu,
