[ https://issues.apache.org/jira/browse/CASSANDRA-8720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302072#comment-14302072 ]
Jonathan Ellis commented on CASSANDRA-8720: ------------------------------------------- In <= 2.0, we log every row larger than in_memory_compaction limit. Isn't that enough? (For 2.1 we should probably add back similar functionality... /cc [~krummas]) > Provide tools for finding wide row/partition keys > ------------------------------------------------- > > Key: CASSANDRA-8720 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8720 > Project: Cassandra > Issue Type: Improvement > Reporter: J.B. Langston > > Multiple users have requested some sort of tool to help identify wide row > keys. They get into a situation where they know a wide row/partition has been > inserted and it's causing problems for them but they have no idea what the > row key is in order to remove it. > Maintaining the widest row key currently encountered and displaying it in > cfstats would be one possible approach. > Another would be an offline tool (possibly an enhancement to sstablekeys) to > show the number of columns/bytes per key in each sstable. If a tool to > aggregate the information at a CF-level could be provided that would be a > bonus, but it shouldn't be too hard to write a script wrapper to aggregate > them if not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)