cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3722) Send Hints to Dynamic Snitch when Compaction or repair is going on for a node.
Date Fri, 30 Mar 2012 22:09:25 GMT


Brandon Williams commented on CASSANDRA-3722:

bq. is it because the lack of a datapoint, isn't taken into account as slowness?

Exactly.  It's not receiving new data, so the score doesn't change and the dead host is still
rated the best until the FD removes it as an option.  Doing it this way, time itself penalizes
the host when it stops responding.
> Send Hints to Dynamic Snitch when Compaction or repair is going on for a node.
> ------------------------------------------------------------------------------
>                 Key: CASSANDRA-3722
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>         Attachments: 0001-CASSANDRA-3722-A1-V2.patch, 0001-CASSANDRA-3722-A1.patch, 0001-CASSANDRA-3722-v3.patch,
0001-CASSANDRA-3723-A2-Patch.patch, 0001-Expose-SP-latencies-in-nodetool-proxyhistograms.txt,
> Currently Dynamic snitch looks at the latency for figuring out which node will be better
serving the requests, this works great but there is a part of the traffic sent to collect
this data... There is also a window when Snitch doesn't know about some major event which
are going to happen on the node (Node which is going to receive the data request).
> It would be great if we can send some sort hints to the Snitch so they can score based
on known events causing higher latencies.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message