cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominic Williams <dwilli...@fightmymonster.com>
Subject Re: How to bring cluster to consistency
Date Mon, 13 Feb 2012 13:19:58 GMT
Hi Nikolay,

Some points that may be useful:

1/ auto_bootstrap = true is used for telling a new node to join the ring
(the cluster). It has nothing to do with hinted handoff

2/ both of your nodes seem to be using the same token? The output indicates
that 100% of your key range is assigned to 10.111.1.141 (and
therefore 10.111.1.142 holds replicas only)

3/ maybe repair is being affected by above, but in my experience it can be
sensitive

On 13 February 2012 13:06, Nikolay Kоvshov <nkovshov@yandex.ru> wrote:

> Hello everybody
>
> I have a very simple cluster containing 2 servers. Replication_factor = 2,
> Consistency_level of reads and writes = 1
>
> 10.111.1.141    datacenter1 rack1       Up     Normal  1.5 TB
>  100.00% vjpigMzv4KkX3x7z
> 10.111.1.142    datacenter1 rack1       Up     Normal  1.41 TB
> 0.00%   聶jpigMzv4KkX3x7z
>
> Note the size please.
>
> Say, server1 cassandra dies and I restart it later. Hinted_handoff =
> enabled, auto_bootstrap = true
>
> During that time server2 received reads and writes. I want changes to be
> copied to server1 when it joins the cluster. As I have replication_factor
> 2, I suppose each data piece should be stored on both servers.
> Auto_bootstrapping doesn't seem to work that way - changed data doesn't
> migrate.
>
> I run nodetool repair and it is always killed by OOM. What else can I do
> to bring cluster to consistency?
>
> Thank you in advance
>

Mime
View raw message