>>> a) how does that setting affect C* in a non-restoring start?
>
> renew_counter_id regenerates a new "NodeId" for the cassandra VM which
> is used to keep track of the counter shards the node holds. If you
> regenerate node ids on each restart, you will most likely corrupt your
> counter data.
writes:
>> restoring a counter column family. I have two questions related to
>> this:
>>
>> a) how does that setting affect C* in a non-restoring start?
renew_counter_id regenerates a new "NodeId" for the cassandra VM which
is used to keep track of the cou
De : mdione@orange.com [mailto:mdione@orange.com]
> restoring a counter column family. I have two questions related to
> this:
>
> a) how does that setting affect C* in a non-restoring start?
>
> b) if it's < bad > (for some value of that), should I stop
According to this post[1], one's supposed to start C* with
-Dcassandra.renew_counter_id=true as one of the steps of
restoring a counter column family. I have two questions related to this:
a) how does that setting affect C* in a non-restoring start?
b) if it's < bad > (f
