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 7BEC41098B for ; Wed, 18 Sep 2013 15:51:35 +0000 (UTC) Received: (qmail 10877 invoked by uid 500); 18 Sep 2013 15:51:30 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 10807 invoked by uid 500); 18 Sep 2013 15:51:29 -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 10799 invoked by uid 99); 18 Sep 2013 15:51:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Sep 2013 15:51:28 +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 nick@datastax.com designates 209.85.212.177 as permitted sender) Received: from [209.85.212.177] (HELO mail-wi0-f177.google.com) (209.85.212.177) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Sep 2013 15:51:23 +0000 Received: by mail-wi0-f177.google.com with SMTP id cb5so6702886wib.10 for ; Wed, 18 Sep 2013 08:51:02 -0700 (PDT) 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=croTI/zrbMNHF0uNAYwjn0tx7QsyohMWLXlCN4GbmSM=; b=AFLjmOaxZ4eSPBIl3FaUKgoG/OuZsM12twGlm/sK6S2meZw+mm+UwEfgWCZJkbJYrw 7p0S3pY/xvt8fmn/t+r/QKp509o3J4UhUI9+5sCsLfFFHpGxsiykS5L98m+gl8bmHbJO zxRMy9FQyay2OjZo7rNE4cAje5mS2KTeA62gY8K3Oq1x/HbCQ43Zl+1cnNssK1NiWppT B8LqmfzNFIrBZxQMHe64n+Ekk1WdElEMzM160QpIHm+niOYYCV86GI2/ma/4W109WRwh KKuwARMpM9lpeRoUsZWxL35ML5C7W5vXhIu9C0zBUhD1gfnHRflGvLmDUFZzXUEGjVMq BM5A== X-Gm-Message-State: ALoCoQkk/7fhGE7P+E/PB4O/xsPB5FdUX+I9REY0TPqJ1tsoCRJDJ2zmMplXZo1ehWf9Ln2WTK4/ X-Received: by 10.180.20.42 with SMTP id k10mr7750407wie.0.1379519462148; Wed, 18 Sep 2013 08:51:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.54.132 with HTTP; Wed, 18 Sep 2013 08:50:41 -0700 (PDT) In-Reply-To: References: From: Nick Bailey Date: Wed, 18 Sep 2013 10:50:41 -0500 Message-ID: Subject: Re: datastax ops center shows a lot of activity when idle To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec53f3959809e2104e6aa67c7 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec53f3959809e2104e6aa67c7 Content-Type: text/plain; charset=ISO-8859-1 OpsCenter's writes for monitoring data will show up in the request/latency graphs yes. 100/sec may be reasonable depending on the number of nodes and columnfamilies OpsCenter is monitoring. On Wed, Sep 18, 2013 at 7:15 AM, Alexander Shutyaev wrote: > Hi all! > > We have experienced a strange issue with datastax opscenter. It showed > much more write requests that we should actually have. We've set everything > up on an isolated node and there without any activity it showed 100+ writes > per second. Is this some opscenter bug? Does it maybe count some internal > cassandra operations? Or maybe the OpsCenter itselft generates such load > because it's saving its monitoring data to the same cassandra it's actually > monitoring? > > Thanks in advance! > --bcaec53f3959809e2104e6aa67c7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
OpsCenter's writes for monitoring data will show up in= the request/latency graphs yes. 100/sec may be reasonable depending on the= number of nodes and columnfamilies OpsCenter is monitoring.


On Wed, Sep 18, 2013 at 7:15 AM, Alexand= er Shutyaev <shutyaev@gmail.com> wrote:
Hi all!

We have experienced a strange i= ssue with datastax opscenter. It showed much more write requests that we sh= ould actually have. We've set everything up on an isolated node and the= re without any activity it showed 100+ writes per second. Is this some opsc= enter bug? Does it maybe count some internal cassandra operations? Or maybe= the OpsCenter itselft generates such load because it's saving its moni= toring data to the same cassandra it's actually monitoring?

Thanks in advance!

--bcaec53f3959809e2104e6aa67c7--