Good point.
> On Jun 27, 2017, at 1:34 PM, Anuj Wadehra <anujw_2...@yahoo.co.in> wrote:
>
> Also, if you restore exactly same data with different IP, you may need to
> clear gossip state on the node.
>
> Anuj
>
> Sent from Yahoo Mail on Android
> <https://overview.mail.yahoo.com/mobile/?.src=Android>
> On Tue, Jun 27, 2017 at 11:56 PM, Anuj Wadehra
> <anujw_2...@yahoo.co.in> wrote:
> Hi Nitan,
>
> I asked for adding autobootstrap false to avoid streaming. Generally,
> replace_address is used for bootstrapping new node with new ip but same token
> range. As you already had data, I asked you to try it with autoboostrap false
> and see if that works for you. If you can bring it back without
> replace_address option, good to go.
>
> Thanks
> Anuj
>
> Sent from Yahoo Mail on Android
> <https://overview.mail.yahoo.com/mobile/?.src=Android>
> On Tue, Jun 27, 2017 at 11:23 PM, Nitan Kainth
> <ni...@bamlabs.com> wrote:
> Anuj,
>
> We did that in past, even if data was not removed, replace_node caused data
> streaming. So changing IP is simplest and safest option.
>
>
>> On Jun 27, 2017, at 12:43 PM, Anuj Wadehra <anujw_2...@yahoo.co.in
>> <mailto:anujw_2...@yahoo.co.in>> wrote:
>>
>> replace_address_first_boot
>
>
