ok, just find it a bit hard to be forced to shutdown the node in case of
an IOException, but I understand why. The exception occurred because of
a missing native snappy library on the server, but the error only occur
because we initialized a column family incorrectly (we are using
cassandra emb
On Wed, May 2, 2012 at 2:42 PM, Mikael Wikblom
wrote:
> Given an IOException in writeSortedContents the latch.countDown() will not
> be called. Wouldn't it be better to place the latch.countDown() in the
> finally statement?
No because having the latch being countDown means 'the sstable has
been
Hi,
(cassandra 1.0.8)
Stumbled on a piece of code in Memtable that looks like it could hang a
thread forever.
public void flushAndSignal(final CountDownLatch latch, ExecutorService
writer, final ReplayPosition context)
{
writer.execute(new WrappedRunnable()
{
