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 5AA3010745 for ; Mon, 28 Oct 2013 21:50:31 +0000 (UTC) Received: (qmail 26936 invoked by uid 500); 28 Oct 2013 21:50:31 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 26915 invoked by uid 500); 28 Oct 2013 21:50:31 -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 26906 invoked by uid 99); 28 Oct 2013 21:50:31 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Oct 2013 21:50:31 +0000 Date: Mon, 28 Oct 2013 21:50:31 +0000 (UTC) From: "Brandon Williams (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (CASSANDRA-6261) Repair should display number of rows that mismatched. 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-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-6261: ------------------------------------------- Assignee: Yuki Morishita > Repair should display number of rows that mismatched. > ------------------------------------------------------ > > Key: CASSANDRA-6261 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6261 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: sankalp kohli > Assignee: Yuki Morishita > Priority: Minor > > Repair currently displays number of ranges which are out of sync. It would be helpful to display how many rows that did not match. > We can do this by sending number of rows with each hash in the Merkle tree. > Also we can put the size of rows which contributed to that hash. > So each leaf node in the tree will have a hash and also the number of rows and its size. > We can also emit the avg rows per hash range and also the min and max. > All this will help in tuning the repair -- This message was sent by Atlassian JIRA (v6.1#6144)