[prev in list] [next in list] [prev in thread] [next in thread]
List: cassandra-user
Subject: Re: [EXTERNAL] Re: Nodetool refresh v/s sstableloader
From: Rajath Subramanyam <rajath26 () gmail ! com>
Date: 2018-08-30 19:23:45
Message-ID: CAATDmt-=P5xhxdMV50Sb-ygTL1JBGtKu_y0BfLUkc+a8PmoM0g () mail ! gmail ! com
[Download RAW message or body]
Thank you, everyone, for responding.
------------------------
Rajath Subramanyam
On Thu, Aug 30, 2018 at 8:38 AM Carl Mueller
<carl.mueller@smartthings.com.invalid> wrote:
> - Range aware compaction strategy that subdivides data by the token range
> could help for this: you only bakcup data for the primary node and not the
> replica data
> - yes, if you want to use nodetool refresh as some sort of recovery
> solution, MAKE SURE YOU STORE THE TOKEN LIST with the
> sstables/snapshots/backups for the nodes.
>
> On Wed, Aug 29, 2018 at 8:57 AM Durity, Sean R <
> SEAN_R_DURITY@homedepot.com> wrote:
>
>> Sstableloader, though, could require a lot more disk space – until
>> compaction can reduce. For example, if your RF=3, you will essentially be
>> loading 3 copies of the data. Then it will get replicated 3 more times as
>> it is being loaded. Thus, you could need up to 9x disk space.
>>
>>
>>
>>
>>
>> Sean Durity
>>
>> *From:* kurt greaves <kurt@instaclustr.com>
>> *Sent:* Wednesday, August 29, 2018 7:26 AM
>> *To:* User <user@cassandra.apache.org>
>> *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 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 <rajath26@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
>>
>>
>>
>>
>>
>> ------------------------------
>>
>> The information in this Internet Email is confidential and may be legally
>> privileged. It is intended solely for the addressee. Access to this Email
>> by anyone else is unauthorized. If you are not the intended recipient, any
>> disclosure, copying, distribution or any action taken or omitted to be
>> taken in reliance on it, is prohibited and may be unlawful. When addressed
>> to our clients any opinions or advice contained in this Email are subject
>> to the terms and conditions expressed in any applicable governing The Home
>> Depot terms of business or client engagement letter. The Home Depot
>> disclaims all responsibility and liability for the accuracy and content of
>> this attachment and for any damages or losses arising from any
>> inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other
>> items of a destructive nature, which may be contained in this attachment
>> and shall not be liable for direct, indirect, consequential or special
>> damages in connection with this e-mail message or its attachment.
>>
>
[Attachment #3 (text/html)]
<div dir="ltr">Thank you, everyone, for responding. <div><br></div><div><div><div \
dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div \
dir="ltr"><div><div>------------------------<br></div>Rajath \
Subramanyam<br></div><div><br></div></div></div></div><br></div></div><br><div \
class="gmail_quote"><div dir="ltr">On Thu, Aug 30, 2018 at 8:38 AM Carl Mueller \
<carl.mueller@smartthings.com.invalid> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">- Range aware compaction strategy that \
subdivides data by the token range could help for this: you only bakcup data for the \
primary node and not the replica data<br>- yes, if you want to use nodetool refresh \
as some sort of recovery solution, MAKE SURE YOU STORE THE TOKEN LIST with the \
sstables/snapshots/backups for the nodes.</div><br><div class="gmail_quote"><div \
dir="ltr">On Wed, Aug 29, 2018 at 8:57 AM Durity, Sean R <<a \
href="mailto:SEAN_R_DURITY@homedepot.com" \
target="_blank">SEAN_R_DURITY@homedepot.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div class="m_-1456646379894372450m_-1875219132947781567m_-7261116089461002228WordSection1">
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Sstableloader, \
though, could require a lot more disk space – until compaction can reduce. For \
example, if your RF=3, you will essentially be loading 3 copies of the data. Then it \
will get replicated 3 more times as it is being loaded. Thus, you could need up to 9x \
disk space. <u></u><u></u></span></p>
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> \
<u></u></span></p> <p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> \
<u></u></span></p> <p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Sean \
Durity<u></u><u></u></span></p> <p class="MsoNormal"><b><span \
style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span \
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> kurt greaves \
<<a href="mailto:kurt@instaclustr.com" \
target="_blank">kurt@instaclustr.com</a>> <br>
<b>Sent:</b> Wednesday, August 29, 2018 7:26 AM<br>
<b>To:</b> User <<a href="mailto:user@cassandra.apache.org" \
target="_blank">user@cassandra.apache.org</a>><br> <b>Subject:</b> [EXTERNAL] Re: \
Nodetool refresh v/s sstableloader<u></u><u></u></span></p> <p \
class="MsoNormal"><u></u> <u></u></p> <div>
<p class="MsoNormal">Removing dev...<u></u><u></u></p>
<div>
<p class="MsoNormal">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.<u></u><u></u></p> </div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p> </div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On 28 August 2018 at 11:27, Rajath Subramanyam <<a \
href="mailto:rajath26@gmail.com" target="_blank">rajath26@gmail.com</a>> \
wrote:<u></u><u></u></p> <blockquote style="border:none;border-left:solid #cccccc \
1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"> <div>
<p class="MsoNormal">Hi Cassandra users, Cassandra dev,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">When recovering using SSTables from a snapshot, I want to know \
what are the key differences between using:<u></u><u></u></p> </div>
<div>
<p class="MsoNormal">1. Nodetool refresh and,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">2. SSTableloader<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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? <u></u><u></u></p> </div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I appreciate any help in advance. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Rajath<u></u><u></u></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">------------------------<u></u><u></u></p>
</div>
<p class="MsoNormal">Rajath Subramanyam<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
The information in this Internet Email is confidential and may be legally privileged. \
It is intended solely for the addressee. Access to this Email by anyone else is \
unauthorized. If you are not the intended recipient, any disclosure, copying, \
distribution or any action taken or omitted to be taken in reliance on it, is \
prohibited and may be unlawful. When addressed to our clients any opinions or advice \
contained in this Email are subject to the terms and conditions expressed in any \
applicable governing The Home Depot terms of business or client engagement letter. \
The Home Depot disclaims all responsibility and liability for the accuracy and \
content of this attachment and for any damages or losses arising from any \
inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a \
destructive nature, which may be contained in this attachment and shall not be liable \
for direct, indirect, consequential or special damages in connection with this e-mail \
message or its attachment.<br> </font>
</div>
</blockquote></div>
</blockquote></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic