Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2D38B17A18 for ; Fri, 27 Mar 2015 17:49:56 +0000 (UTC) Received: (qmail 37510 invoked by uid 500); 27 Mar 2015 17:49:56 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 37474 invoked by uid 500); 27 Mar 2015 17:49:56 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 37460 invoked by uid 99); 27 Mar 2015 17:49:55 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Mar 2015 17:49:55 +0000 Date: Fri, 27 Mar 2015 17:49:55 +0000 (UTC) From: "Philip Thompson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8381) CFStats should record keys of largest N requests for time interval MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-8381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384233#comment-14384233 ] Philip Thompson commented on CASSANDRA-8381: -------------------------------------------- Bump. [~mstump], should we close as duplicate of CASSANDRA-7974? > CFStats should record keys of largest N requests for time interval > ------------------------------------------------------------------ > > Key: CASSANDRA-8381 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8381 > Project: Cassandra > Issue Type: Improvement > Reporter: Matt Stump > Priority: Critical > > Isolating the problem partition for a CF is right now incredibly difficult. If we could keep the primary key of the largest N read or write requests for the pervious interval or since counter has been cleared it would be extremely useful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)