On Wed, Oct 22, 2014 at 7:58 AM, Li, George
wrote:
> I assume that you are restoring snapshot data onto a new ring with the
> same topology (i.e. if the old ring has n nodes, your new ring has n nodes
> also). I discussed this a consultant from DataStax, and he told me that I
> need to make sure
I assume that you are restoring snapshot data onto a new ring with the same
topology (i.e. if the old ring has n nodes, your new ring has n nodes
also). I discussed this a consultant from DataStax, and he told me that I
need to make sure each new node in the new ring need to have the same token
lis
On Thu, Oct 16, 2014 at 4:17 PM, Bosung Seo wrote:
> I upgraded my Cassandra ring and restored data(copying snapshots) from the
> old ring. I am currently running the nodetool repair.
> I count the tables to check every rows is in the table, but counts have
> different values.
> It contains 571 r
I upgraded my Cassandra ring and restored data(copying snapshots) from the
old ring. I am currently running the nodetool repair.
I count the tables to check every rows is in the table, but counts have
different values.
It contains 571 rows, and counts are 500, 530, 501, and so on. Should I
wait unt
