cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-5550) nodetool repair hanging on multi sites config
Date Wed, 08 May 2013 14:43:16 GMT


Jonathan Ellis resolved CASSANDRA-5550.

    Resolution: Duplicate
> nodetool repair hanging on multi sites config
> ---------------------------------------------
>                 Key: CASSANDRA-5550
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.2.4
>            Reporter: Kévin LOVATO
> We recently added a new datacenter to our cluster, and we want some keyspaces to be replicated
to it, but not all.
> So some of our Keyspaces have a replication factor of {code}{ dcMain: 3, dcNew: 1 }{code}and
some have {code}{ dcMain: 3 }{code}We then ran a nodetool repair on one of the new servers
so the data would be replicated correctly, but it just hung.
> After some investigation, we saw that if a Keyspace didn't have replication info for
dcNew, or a replication factor of 0, a nodetool repair from the new servers would hang (nothing
concerning repair in the logs, not even in DEBUG level).
> On the other hand, it works properly if the Keyspace has a replica in dcNew or if the
repair is called from dcMain.
> We might be doing something wrong, but I don't think nodetool should hang silently even
if something is going wrong.
> Nodetool repair -pr also works in all situations, but it seems that it is not copying
the data to the new datacenter at all, it runs and logs that the keyspace is up to date after
receiving the merkle trees, even though nothing is actually copied on the disk, even after
flushing (maybe an unrelated issue, should I open another ticket?).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message