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

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis commented on CASSANDRA-5135:
-------------------------------------------

I think you want a DTPE not a JMXETPE.  You'll still need to setRejectedExecutionHandler(DiscardPolicy) but you won't get the extra onInitialRejection baggage from JMXETPE.

Do we need to update RING_DELAY to accomodate long cPR times?

Nit: just use List.size instead of counting the tables processed


                
> 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