Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <1358895434879-7584954.post@n2.nabble.com>
References: <1358859798922-7584932.post@n2.nabble.com>
	<CACHzRHY2drm1xzuBZMbAke15akGZ3sWcRZJr=ui0kmBy76iv=w@mail.gmail.com>
	<1358895434879-7584954.post@n2.nabble.com>
Date: Tue, 22 Jan 2013 17:12:32 -0800
Message-ID: 
 <CACHzRHZ4VDoMNaNhMqpi0=AuMfND=FW5Ew2EbmP=-k3sEdRdSw@mail.gmail.com>
Subject: Re: node down = log explosion?
From: Rob Coli <rcoli@palominodb.com>
To: user@cassandra.apache.org
Cc: cassandra-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jan 22, 2013 at 2:57 PM, Sergey Olefir <solf.lists@gmail.com> wrote:
> Do you have a suggestion as to what could be a better fit for counters?
> Something that can also replicate across DCs and survive link breakdown
> between nodes (across DCs)? (and no, I don't need 100.00% precision
> (although it would be nice obviously), I just need to be "pretty close" for
> the values of "pretty")

In that case, Cassandra counters are probably fine.

> On the subject of bug report -- I probably will -- but I'll wait a bit for
> more info here, perhaps there's some configuration or something that I just
> don't know about.

Excepting on replicateOnWrite stage seems pretty unambiguous to me,
and unexpected. YMMV?

=Rob

-- 
=Robert Coli
AIM&GTALK - rcoli@palominodb.com
YAHOO - rcoli.palominob
SKYPE - rcoli_palominodb