cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5241) Fix forceBlockingFlush
Date Sat, 16 Feb 2013 17:51:13 GMT


Sylvain Lebresne commented on CASSANDRA-5241:

Would you have steps to reproduce?

Also, what do you mean by "there was a migration every second"? Cause the log you posted above
doesn't mention "migration" per se, nor in itself exhibit any particular looping.

Also not really sure this is related to this ticket, but in any case if you're experiencing
some looping, something's wrong.
> Fix forceBlockingFlush
> ----------------------
>                 Key: CASSANDRA-5241
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Marcus Eriksson
>             Fix For: 1.2.2
>         Attachments: 0001-CASSANDRA-5241-wait-for-flushing-to-complete-before-.patch
> ForceBlockingFlush doesn't guarantee that after the call, every that the thread has written
prior to the call will be fully flushed. At least not in the case of concurrent flushes, because
if 2 threads flush roughly at the same time, one will have it's forceBlockingFlush call return
immediately because the memtable will be clean (even though some of the thread writes may
have not be fully flushed yet).
> I think this is very fragile and make it easy to have hard to find races and so we should
fix it. Typically a forceFlush that see a clean memtable could submit a dummy task in the
postFlushExecutor and wait for that.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message