You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Rick Branson (Commented) (JIRA)" <ji...@apache.org> on 2011/11/30 21:31:40 UTC
[jira] [Commented] (CASSANDRA-3543) Infinite hang during shutdown
[ https://issues.apache.org/jira/browse/CASSANDRA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160307#comment-13160307 ]
Rick Branson commented on CASSANDRA-3543:
-----------------------------------------
This is a bug in the new commit log allocator from #3411. The MutationStage threads are all blocked because the CommitLogExecutor queue is full. The COMMIT-LOG-WRITER thread which drains this queue is blocking on fetchSegment() which waits on CommitLogAllocator to push newly created segments onto this queue. Brandon also stated that only 1 commit log segment existed afterwards.
> Infinite hang during shutdown
> -----------------------------
>
> Key: CASSANDRA-3543
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3543
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Brandon Williams
> Attachments: hung_stack.txt
>
>
> While testing CASSANDRA-3541 at some point stress completely timed out. I proceeded to shut the cluster down and 2/3 JVMs hang infinitely. After a while, one of them logged:
> {noformat}
> WARN 19:07:50,133 Some hints were not written before shutdown. This is not supposed to happen. You should (a) run repair, and (b) file a bug report
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira