Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 64494 invoked from network); 12 May 2010 18:10:47 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 May 2010 18:10:47 -0000 Received: (qmail 78921 invoked by uid 500); 12 May 2010 18:10:46 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 78899 invoked by uid 500); 12 May 2010 18:10:46 -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 78891 invoked by uid 99); 12 May 2010 18:10:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 18:10:46 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jamesgolick@gmail.com designates 209.85.211.190 as permitted sender) Received: from [209.85.211.190] (HELO mail-yw0-f190.google.com) (209.85.211.190) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 18:10:41 +0000 Received: by ywh28 with SMTP id 28so149623ywh.28 for ; Wed, 12 May 2010 11:10:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=YvfeNid1c2NpuzS/3nHQbMhCmGD7e/f4fgQ1wgRtSe0=; b=Hf0wzRJKL92cl1tb2icqqwBvzyMaPs3sEymQRfT4BDTTDGJ8OgBFk9eO7hJLMCwJoD UkgNK/DEpEjqzMMRc6eL6dOG3vVHphS6ls9RCyJ7BtZmyqWyt1o/Bs5g/dWDpA1eohx6 gur8+gVvO5c3bdyGDwCMuBS0mdvMyDRF/XLmo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Op2X2YD3ASVr6zbGuCQTIhfEN48CCHa1NGVJbcGs6Kfv1MvJe8OTUfmKRvUDAvYTVS 4EhHFatH5pzVY6MABg7JPjnxyx5551gIpav1WnXXCrgeY4g4a9aDBqfcDlQmaoUyQ8oQ wyJMSJCHJ+uNcPT5ZFjjrDnFMTt1O7Y9wxwl4= MIME-Version: 1.0 Received: by 10.101.4.18 with SMTP id g18mr4619133ani.39.1273687817935; Wed, 12 May 2010 11:10:17 -0700 (PDT) Received: by 10.100.240.16 with HTTP; Wed, 12 May 2010 11:10:17 -0700 (PDT) In-Reply-To: References: Date: Wed, 12 May 2010 11:10:17 -0700 Message-ID: Subject: Re: Cache capacities set by nodetool From: James Golick To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001636c5bdb0f16c930486698d18 --001636c5bdb0f16c930486698d18 Content-Type: text/plain; charset=ISO-8859-1 Hmmm.... that's definitely what we're seeing. Although, we aren't seeing cache settings being picked up properly on a restart either. On Wed, May 12, 2010 at 8:42 AM, Ryan King wrote: > It's a bug: > > https://issues.apache.org/jira/browse/CASSANDRA-1079 > > -ryan > > On Wed, May 12, 2010 at 8:16 AM, James Golick > wrote: > > When I first brought this cluster online, the storage-conf.xml file had a > > few cache capacities set. Since then, we've completely changed how we use > > cassandra's caching, and no longer use any of the caches I setup in the > > original configuration. > > I'm finding that cassandra doesn't want to keep my new cache settings. I > can > > disable those caches with setcachecapacity, check cfstats and see that > they > > are disabled, but within a few minutes, cfstats is reporting that the > caches > > are back. > > Anything I can do? > --001636c5bdb0f16c930486698d18 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hmmm.... that's definitely what we're seeing. Although, we aren'= ;t seeing cache settings being picked up properly on a restart either.
<= br>
On Wed, May 12, 2010 at 8:42 AM, Ryan King <ryan@twitter.com> wrote:
It's a bug:

https://issues.apache.org/jira/browse/CASSANDRA-1079

-ryan

On Wed, May 12, 2010 at 8:16 AM, James Golick <jamesgolick@gmail.com> wrote:
> When I first brought this cluster online, the storage-conf.xml file ha= d a
> few cache capacities set.=A0Since then, we've completely changed h= ow we use
> cassandra's caching, and no longer use any of the caches I setup i= n the
> original configuration.
> I'm finding that cassandra doesn't want to keep my new cache s= ettings. I can
> disable those caches with setcachecapacity, check cfstats and see that= they
> are disabled, but within a few minutes, cfstats is reporting that the = caches
> are back.
> Anything I can do?

--001636c5bdb0f16c930486698d18--