ould need up to 9x disk space.
>>
>>
>>
>>
>>
>> Sean Durity
>>
>> *From:* kurt greaves
>> *Sent:* Wednesday, August 29, 2018 7:26 AM
>> *To:* User
>> *Subject:* [EXTERNAL] Re: Nodetool refresh v/s sstableloader
>>
>>
>&g
ed 3 more times as
> it is being loaded. Thus, you could need up to 9x disk space.
>
>
>
>
>
> Sean Durity
>
> *From:* kurt greaves
> *Sent:* Wednesday, August 29, 2018 7:26 AM
> *To:* User
> *Subject:* [EXTERNAL] Re: Nodetool refresh v/s sstableloader
>
>
>
: kurt greaves
Sent: Wednesday, August 29, 2018 7:26 AM
To: User
Subject: [EXTERNAL] Re: Nodetool refresh v/s sstableloader
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
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
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
