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 (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2011/11/30 23:31:41 UTC
[jira] [Issue Comment Edited] (CASSANDRA-3543) Commit Log Allocator
deadlock during shutdown
[ https://issues.apache.org/jira/browse/CASSANDRA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160391#comment-13160391 ]
Rick Branson edited comment on CASSANDRA-3543 at 11/30/11 10:31 PM:
--------------------------------------------------------------------
Steps to reproduce:
1) $ rm -rf /var/lib/cassandra/*
2) Start Cassandra
3) $ stress -F1 -n 999999999
The stress will run until requests start timing out, on my box it was ~400,000.
was (Author: rbranson):
Steps to reproduce:
1) $ rm -rf /var/lib/cassandra/*
2) Start Cassandra
3) $ stress -F1 -C 999999999
The stress will run until requests start timing out, on my box it was ~400,000.
> Commit Log Allocator deadlock during shutdown
> ---------------------------------------------
>
> Key: CASSANDRA-3543
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3543
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1
> Reporter: Brandon Williams
> Assignee: Rick Branson
> 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