cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lohfink (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7974) Enable tooling to detect hot partitions
Date Wed, 21 Jan 2015 17:38:36 GMT

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

Chris Lohfink updated CASSANDRA-7974:
-------------------------------------
    Attachment: CASSANDRA-7974v5.txt

Fixed in v5 an issue - the byte array it was using was not checked for equality in the StreamSummary
so the same key may show up as duplicates.

> Enable tooling to detect hot partitions
> ---------------------------------------
>
>                 Key: CASSANDRA-7974
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7974
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Brandon Williams
>            Assignee: Chris Lohfink
>             Fix For: 2.1.3
>
>         Attachments: 7974.txt, CASSANDRA-7974v3.txt, CASSANDRA-7974v4.txt, CASSANDRA-7974v5.txt,
cassandra-2.1-7974v2.txt
>
>
> Sometimes you know you have a hot partition by the load on a replica set, but have no
way of determining which partition it is.  Tracing is inadequate for this without a lot of
post-tracing analysis that might not yield results.  Since we already include stream-lib for
HLL in compaction metadata, it shouldn't be too hard to wire up topK for X seconds via jmx/nodetool
and then return the top partitions hit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message