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 053A0D2CC for ; Thu, 11 Oct 2012 20:47:27 +0000 (UTC) Received: (qmail 14061 invoked by uid 500); 11 Oct 2012 20:47:24 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 14035 invoked by uid 500); 11 Oct 2012 20:47: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 14027 invoked by uid 99); 11 Oct 2012 20:47:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2012 20:47:24 +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 (athena.apache.org: domain of tyler@datastax.com designates 209.85.220.172 as permitted sender) Received: from [209.85.220.172] (HELO mail-vc0-f172.google.com) (209.85.220.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2012 20:47:19 +0000 Received: by mail-vc0-f172.google.com with SMTP id fl11so3018406vcb.31 for ; Thu, 11 Oct 2012 13:46:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=gmrTLn0iJI/N3TgApQE6cvW+CZZh21ZLJ+Yy149Ui48=; b=J9bPGBPcnKDm4dtYmwp+5a4pXIhWGOX1pAgotMs0TVrUofFcgk7Mo1SJ+l6YX84HLk rBClW7HPlKeWNi6ewAn+MJ3uNVVjPcbVjOzcmKaq3Bq6RvF4x/NXoK8bL6hqe2ZpCk0c HTw0rA+olyd2pxx5eew0cDjIXxr69p9lsbUDQIF8N24ndtiEkYJsX0KaGChMsrMpktk8 CZSatAy+dGmH0BH78peLrfJ4zs4fJ0Vddu9QKO9s3XQ4iGzkeKy6DNBs8Go/ODoNGWr/ s09LvQ7aABJhOV5HeARx9RvxOFjkH48o4alucyR8q5OvBCmQae+2Sy5KtnIDdOdr7wgn oTBg== MIME-Version: 1.0 Received: by 10.52.74.97 with SMTP id s1mr986931vdv.100.1349988419232; Thu, 11 Oct 2012 13:46:59 -0700 (PDT) Received: by 10.58.226.228 with HTTP; Thu, 11 Oct 2012 13:46:59 -0700 (PDT) In-Reply-To: References: <19C8179E-1594-4190-AB19-4F57328B03AF@thelastpickle.com> Date: Thu, 11 Oct 2012 15:46:59 -0500 Message-ID: Subject: Re: READ messages dropped From: Tyler Hobbs To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec501669d2de24504cbceac0f X-Gm-Message-State: ALoCoQnvBGTOv3gC9VIyfGeSRi0LjP39XTbohIaM7ToWz0241DFLLL9jmMIKdD9K1Y/TYp3iBCYu X-Virus-Checked: Checked by ClamAV on apache.org --bcaec501669d2de24504cbceac0f Content-Type: text/plain; charset=ISO-8859-1 On Wed, Oct 10, 2012 at 3:10 PM, Tamar Fraenkel wrote: > > What I did noticed while looking at the logs (which are also running > OpsCenter), is that there is some correlation between the dropped reads and > flushes of OpsCenter column families to disk and or compactions. What are > the rollups CFs? why is there so much traffic in them? The rollups CFs hold the performance metric data that OpsCenter stores about your cluster. Typically these aren't actually very high traffic column families, but that depends on how many column families you have (more CFs require more metrics to be stored). If you have a lot of column families, you have a couple of options for reducing the amount of metric data that's stored: http://www.datastax.com/docs/opscenter/trouble_shooting_opsc#limiting-the-metrics-collected-by-opscenter Assuming you don't have a large number of CFs, your nodes may legitimately be nearing capacity. -- Tyler Hobbs DataStax --bcaec501669d2de24504cbceac0f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Wed, Oct 10, 2012 at 3:10 PM, Tamar Fraenkel = <tamar@tok-media.com> wrote:

What I did noticed while looking at the logs (which are also running Op= sCenter), is that there is some correlation between the dropped reads and f= lushes of OpsCenter column families to disk and or compactions. What are th= e rollups CFs? why is there so much traffic in them?

The rollups CFs hold the performance metric data that OpsCenter s= tores about your cluster.=A0 Typically these aren't actually very high = traffic column families, but that depends on how many column families you h= ave (more CFs require more metrics to be stored).=A0 If you have a lot of c= olumn families, you have a couple of options for reducing the amount of met= ric data that's stored: http:= //www.datastax.com/docs/opscenter/trouble_shooting_opsc#limiting-the-metric= s-collected-by-opscenter

Assuming you don't have a large number of CFs, your nodes may legit= imately be nearing capacity.

--
Tyler Hobbs
DataStax
<= br> --bcaec501669d2de24504cbceac0f--