Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70E989B0C for ; Wed, 21 Dec 2011 01:45:11 +0000 (UTC) Received: (qmail 83611 invoked by uid 500); 21 Dec 2011 01:45:09 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 83538 invoked by uid 500); 21 Dec 2011 01:45:09 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 83530 invoked by uid 99); 21 Dec 2011 01:45:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Dec 2011 01:45:09 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bstarkenburg@gmail.com designates 74.125.82.172 as permitted sender) Received: from [74.125.82.172] (HELO mail-we0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Dec 2011 01:45:04 +0000 Received: by werb14 with SMTP id b14so2784323wer.31 for ; Tue, 20 Dec 2011 17:44:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=/fxpA2KLKRhfJN2sNDt5D8GU6CychFMRsDIyyYs3URg=; b=AGwAiHXoQG55WlZzXB7F0hb9FOOPq+xw10R6Hf57/i0+iz4SmqExOSGeEteZFbfIid 5BVoVwIgg9XEDlauUt7Cp2GSxYGWsx3JlaQf0EROZi4xHVwE/TE8LL7IdWiywxxmnuz+ AwW+0vODEeuOulH1L57DOdWgoy6o1oHfHml9I= MIME-Version: 1.0 Received: by 10.216.132.139 with SMTP id o11mr2462573wei.33.1324431883221; Tue, 20 Dec 2011 17:44:43 -0800 (PST) Received: by 10.223.78.199 with HTTP; Tue, 20 Dec 2011 17:44:43 -0800 (PST) Date: Tue, 20 Dec 2011 17:44:43 -0800 Message-ID: Subject: Routine nodetool repair From: Blake Starkenburg To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0016e6de0407edbb6b04b49053b3 --0016e6de0407edbb6b04b49053b3 Content-Type: text/plain; charset=ISO-8859-1 I have been playing around with Cassandra for a few months now. Starting to explore more of the routine maintenance and backup strategies and I have a general question about nodetool repair. After reading the following page: http://www.datastax.com/docs/0.8/operations/cluster_management it has occurred to me that for these past few months I have NOT DONE any cleanup or repair commands on a test 2-node cluster (and their has been quite a few deletes, writes, etc.). For some reason I was under the assumption that Cassandra handled the tombstone records from deletes automatically? Should I still run nodetool repair and if so, what about old deletes which occurred months ago? Thank You! --0016e6de0407edbb6b04b49053b3 Content-Type: text/html; charset=ISO-8859-1 I have been playing around with Cassandra for a few months now. Starting to explore more of the routine maintenance and backup strategies and I have a general question about nodetool repair. After reading the following page: http://www.datastax.com/docs/0.8/operations/cluster_management it has occurred to me that for these past few months I have NOT DONE any cleanup or repair commands on a test 2-node cluster (and their has been quite a few deletes, writes, etc.).

For some reason I was under the assumption that Cassandra handled the tombstone records from deletes automatically? Should I still run nodetool repair and if so, what about old deletes which occurred months ago?

Thank You! --0016e6de0407edbb6b04b49053b3--