cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5135) calculatePendingRanges could be asynchronous
Date Fri, 11 Jan 2013 22:30:13 GMT


Jonathan Ellis commented on CASSANDRA-5135:

You might want to extend the handler to count rejection stats the way our default one does,
but either way +1 from me.
> calculatePendingRanges could be asynchronous
> --------------------------------------------
>                 Key: CASSANDRA-5135
>                 URL:
>             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, 5135-v2.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
> 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:

View raw message