Thanks for the response guys. Let me try setting token ranges manually and move the data again to correct nodes. Will update with the outcome soon.
On Tue, Apr 17, 2018 at 5:42 AM, kurt greaves <k...@instaclustr.com> wrote: > Sorry for the delay. > >> Is the problem related to token ranges? How can I find out token range >> for each node? >> What can I do to further debug and root cause this? > > Very likely. See below. > > My previous cluster has 3 nodes but replication factor is 2. I am not >> exactly sure how I would handle the tokens. Can you explain that a bit? > > The new cluster will have to have the same token ring as the old if you > are copying from node to node. Basically you should get the set of tokens > for each node (from nodetool ring) and when you spin up your 3 new nodes, > set initial_tokens in the yaml to be the comma-separated list of tokens for > *exactly > one* node from the previous cluster. When restoring the SSTables you need > to make sure you take the SSTables from the original node and place it on > the new node that has the *same* list of tokens. If you don't do this it > won't be a replica for all the data in those SSTables and consequently > you'll lose data (or it simply won't be available). > > -- Faraz Mateen
