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 D0332109A2 for ; Fri, 22 Nov 2013 05:01:32 +0000 (UTC) Received: (qmail 85942 invoked by uid 500); 22 Nov 2013 05:01:30 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 85576 invoked by uid 500); 22 Nov 2013 05:01:24 -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 85568 invoked by uid 99); 22 Nov 2013 05:01:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Nov 2013 05:01:23 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rmenon@apigee.com designates 209.85.223.177 as permitted sender) Received: from [209.85.223.177] (HELO mail-ie0-f177.google.com) (209.85.223.177) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Nov 2013 05:01:17 +0000 Received: by mail-ie0-f177.google.com with SMTP id tp5so1322779ieb.36 for ; Thu, 21 Nov 2013 21:00:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=Zd3usYUZD+9G87fkKGj7oqM+9gpHXjewEfCrocjU/R0=; b=N2rtM0aA1ZKkGwo1ZUsGA+TN3M4WdNSMl2ZxAIzRcGOueT9u2K+t6FmFHFrolQBCG1 ufD7cDaMoQgHRnSe5ftqiegIFEEMntyZKCEXhcF6BWs3D7dWBHlJyiChLK5t1C1JvEv4 MqIGcrqNdLWG0LadIXd9GEqD7yNCyMKKA1ocQTRmq78pO1De1gNwBy8lIZhPPj0nOdiq UYSC/6EEoScBBZ9OHMLNn15tpCs6vrnfPtrRhIDnSR7zj754YvADfkbj8L53FDTk8sIz x+8QTNZPHrqSRa0Xzao8KkdkZiWhXU2wnlJRPSWPqeadI7fqNATG0ulAW/S/jTRk8wGL oL4w== X-Gm-Message-State: ALoCoQlmWs6E3iI2/P4WN71UkupoYF84SWQDbRRN0CESXIB57jVLUbnhgMO6J/z5oyQqBUXS2GGd X-Received: by 10.43.73.197 with SMTP id yt5mr6852202icb.0.1385096455398; Thu, 21 Nov 2013 21:00:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.179.9 with HTTP; Thu, 21 Nov 2013 21:00:35 -0800 (PST) In-Reply-To: References: From: Rahul Menon Date: Fri, 22 Nov 2013 10:30:35 +0530 Message-ID: Subject: Re: 1.1.11: system keyspace is filling up To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11c2190a34458204ebbce6f2 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2190a34458204ebbce6f2 Content-Type: text/plain; charset=ISO-8859-1 Oleg, The system keyspace is not replicated it is local to the node. You should check your logs to see if there are Timeouts from streaming hints, i believe the default value to stream hints it 10 seconds. When i ran into this problem i truncated hints to clear out the space and then ran a repair so ensure that all the data was consistant across all nodes, even if there was a failure. -rm On Tue, Nov 5, 2013 at 6:29 PM, Oleg Dulin wrote: > What happens if they are not being successfully delivered ? Will they > eventually TTL-out ? > > > Also, do I need to truncate hints on every node or is it replicated ? > > > Oleg > > > On 2013-11-04 21:34:55 +0000, Robert Coli said: > > > On Mon, Nov 4, 2013 at 11:34 AM, Oleg Dulin wrote: > > I have a dual DC setup, 4 nodes, RF=4 in each. > > > The one that is used as primary has its system keyspace fill up with 200 > gigs of data, majority of which is hints. > > > Why does this happen ? > > > How can I clean it up ? > > > If you have this many hints, you probably have flapping / frequent network > partition, or very overloaded nodes. If you compare the number of hints to > the number of dropped messages, that would be informative. If you're > hinting because you're dropping, increase capacity. If you're hinting > because of partition, figure out why there's so much partition. > > > WRT cleaning up hints, they will automatically be cleaned up eventually, > as long as they are successfully being delivered. If you need to manually > clean them up you can truncate system.hints keyspace. > > > =Rob > > > > > > > -- > > Regards, > > Oleg Dulin > > http://www.olegdulin.com > --001a11c2190a34458204ebbce6f2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Oleg,=A0

The system keyspace is not replicated it is local to the node. You should c= heck your logs to see if there are Timeouts from streaming hints, i believe= the default value to stream hints it 10 seconds. When i ran into this prob= lem i truncated hints to clear out the space and then ran a repair so ensur= e that all the data was consistant across all nodes, even if there was a fa= ilure.=A0

-rm=A0
--001a11c2190a34458204ebbce6f2--