cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3882) avoid distributed deadlock in migration stage
Date Thu, 10 May 2012 16:18:53 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272454#comment-13272454
] 

Jonathan Ellis commented on CASSANDRA-3882:
-------------------------------------------

My intention was only to clarify what problem we're trying to solve here, so everyone doesn't
have to xref w/ 3832.
                
> avoid distributed deadlock in migration stage
> ---------------------------------------------
>
>                 Key: CASSANDRA-3882
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3882
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Peter Schuller
>            Assignee: Peter Schuller
>         Attachments: CASSANDRA-3882-hack.txt
>
>
> This is follow-up work for the remainders of CASSANDRA-3832 which was only a partial
fix. The deadlock in the migration stage needs to be fixed, as it can cause bootstrap (at
least) to take potentially a very very long time to complete, and might also cause a lack
of schema propagation until otherwise "poked".

--
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

        

Mime
View raw message