You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2013/01/09 16:00:18 UTC

[jira] [Updated] (CASSANDRA-5135) calculatePendingRanges could be asynchronous

     [ https://issues.apache.org/jira/browse/CASSANDRA-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams updated CASSANDRA-5135:
----------------------------------------

    Attachment: 5135.txt

Patch to signal the executor to recalculate in handleState* and then wait it in places where we expect it to be completed.
                
> calculatePendingRanges could be asynchronous
> --------------------------------------------
>
>                 Key: CASSANDRA-5135
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5135
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>             Fix For: 1.1.9
>
>         Attachments: 5135.txt
>
>
> In the vein of CASSANDRA-3881, cPR is expensive and can end up dominating the gossip thread, causing all sorts of havoc.  One simple way we can triage this is to simply give it it's own executor with a queue size of 1 (since we don't actually need to recalculate for every host we see if we suddenly see many of them) and do the calculation asynchronously, freeing up the gossiper.

--
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: http://www.atlassian.com/software/jira