On Thu, Jun 13, 2019 at 3:41 PM Jeff Jirsa wrote:
>
> Bootstrapping a new node does not require repairs at all.
>
Was my understanding as well.
Replacing a node only requires repairs to guarantee consistency to avoid
> violating quorum because streaming for bootstrap only streams from one
>
> On Jun 13, 2019, at 6:29 AM, Oleksandr Shulgin
> wrote:
>
>> On Thu, Jun 13, 2019 at 3:16 PM Jeff Jirsa wrote:
>
>> On Jun 13, 2019, at 2:52 AM, Oleksandr Shulgin
>> wrote:
>> On Wed, Jun 12, 2019 at 4:02 PM Jeff Jirsa wrote:
To avoid violating consistency guarantees, you have to
On Thu, Jun 13, 2019 at 3:16 PM Jeff Jirsa wrote:
> On Jun 13, 2019, at 2:52 AM, Oleksandr Shulgin <
> oleksandr.shul...@zalando.de> wrote:
> On Wed, Jun 12, 2019 at 4:02 PM Jeff Jirsa wrote:
>
> To avoid violating consistency guarantees, you have to repair the replicas
>> while the lost node
> On Jun 13, 2019, at 2:52 AM, Oleksandr Shulgin
> wrote:
>
>> On Wed, Jun 12, 2019 at 4:02 PM Jeff Jirsa wrote:
>
>> To avoid violating consistency guarantees, you have to repair the replicas
>> while the lost node is down
>
> How do you suggest to trigger it? Potentially replicas of
On Wed, Jun 12, 2019 at 4:02 PM Jeff Jirsa wrote:
> To avoid violating consistency guarantees, you have to repair the replicas
> while the lost node is down
>
How do you suggest to trigger it? Potentially replicas of the primary
range for the down node are all over the local DC, so I would go
me companies that provide finer-grained backup and recovery
> options, though.
>
>
>
> Sean Durity
>
>
>
> *From:* Alan Gano
> *Sent:* Wednesday, June 12, 2019 1:43 PM
> *To:* user@cassandra.apache.org
> *Subject:* [EXTERNAL] RE: Recover lost node from backup or ev
to hold some level of backups.
There are some companies that provide finer-grained backup and recovery
options, though.
Sean Durity
From: Alan Gano
Sent: Wednesday, June 12, 2019 1:43 PM
To: user@cassandra.apache.org
Subject: [EXTERNAL] RE: Recover lost node from backup or evict/re-add
nodetool repair?).
Thanks,
Alan Gano
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Wednesday, June 12, 2019 10:14 AM
To: user@cassandra.apache.org
Subject: Re: Recover lost node from backup or evict/re-add?
A host can replace itself using the method I described
On Jun 12, 2019, at 7:10 AM
.com]
> Sent: Wednesday, June 12, 2019 10:02 AM
> To: user@cassandra.apache.org
> Subject: Re: Recover lost node from backup or evict/re-add?
>
> To avoid violating consistency guarantees, you have to repair the replicas
> while the lost node is down
>
> Once you do that
– e, does it
get caught up after a restore and start it up?
Alan
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Wednesday, June 12, 2019 10:02 AM
To: user@cassandra.apache.org
Subject: Re: Recover lost node from backup or evict/re-add?
To avoid violating consistency guarantees, you have
To avoid violating consistency guarantees, you have to repair the replicas
while the lost node is down
Once you do that it’s typically easiest to bootstrap a replacement (there’s a
property named “replace address first boot” you can google or someone can link)
that tells a new joining host to
If I lose a node, does it make sense to even restore from
snapshot/incrementals/commitlogs?
Or is the best way to do an evict/re-add?
Thanks,
Alan.
NOTICE: This communication is intended only for the person or entity to whom it
is addressed and may contain confidential, proprietary, and/or
12 matches
Mail list logo
