You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by DE VITO Dominique <do...@thalesgroup.com> on 2013/01/07 18:05:52 UTC

replace_token versus nodetool repair

Hi,

Is "nodetool repair" only usable if the node to repair has a valid (= up-to-date with its neighbors) schema?

If the data records are completely broken on a node with <token>, is it valid to clean the (data) records and to execute replace_token=<token> on the *same* node?

Thanks.

Regards,
Dominique


Re: replace_token versus nodetool repair

Posted by Rob Coli <rc...@palominodb.com>.
On Mon, Jan 7, 2013 at 9:05 AM, DE VITO Dominique
<do...@thalesgroup.com> wrote:
> Is "nodetool repair" only usable if the node to repair has a valid (= up-to-date with its neighbors) schema?

If the node is in the cluster, it should have the correct schema. If
it doesn't have the correct schema, you should either wait until the
schema is received, or (if it's "stuck") wipe the schema on that node
and re-join the node.

> If the data records are completely broken on a node with <token>, is it valid to clean the (data) records and to execute replace_token=<token> on the *same* node?

Yes.

=Rob

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