Removing dev... Nodetool refresh only picks up new SSTables that have been placed in the tables directory. It doesn't account for actual ownership of the data like SSTableloader does. Refresh will only work properly if the SSTables you are copying in are completely covered by that nodes tokens. It doesn't work if there's a change in topology, replication and token ownership will have to be more or less the same.
SSTableloader will break up the SSTables and send the relevant bits to whichever node needs it, so no need for you to worry about tokens and copying data to the right places, it will do that for you. On 28 August 2018 at 11:27, Rajath Subramanyam <rajat...@gmail.com> wrote: > Hi Cassandra users, Cassandra dev, > > When recovering using SSTables from a snapshot, I want to know what are > the key differences between using: > 1. Nodetool refresh and, > 2. SSTableloader > > Does nodetool refresh have restrictions that need to be met? > Does nodetool refresh work even if there is a change in the topology > between the source cluster and the destination cluster? Does it work if the > token ranges don't match between the source cluster and the destination > cluster? Does it work when an old SSTable in the snapshot has a dropped > column that is not part of the current schema? > > I appreciate any help in advance. > > Thanks, > Rajath > ------------------------ > Rajath Subramanyam > >
