Haddad mailto:j...@jonhaddad.com>>
Sent: Friday, December 20, 2019 2:13 PM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Streaming Failed during bootstrap of a Replacement node
This email is from an external source - exercise caution regarding links and
atta
n,
>
> Yes we will upgrade it soon. But before we can upgrade shouldn’t we get
> this lost node in the cluster to be replaced ?
>
>
>
>
>
>
>
> *From:* Jon Haddad
> *Sent:* Friday, December 20, 2019 2:13 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re:
Hi Jon,
Yes we will upgrade it soon. But before we can upgrade shouldn’t we get this
lost node in the cluster to be replaced ?
From: Jon Haddad
Sent: Friday, December 20, 2019 2:13 PM
To: user@cassandra.apache.org
Subject: Re: Streaming Failed during bootstrap of a Replacement node
This
You should upgrade to Cassandra 3.11.5 before doing anything else. You're
running a pretty old and buggy version. There's been hundreds (maybe
thousands) of bugs fixed between 3.3 and 3.11.5.
On Fri, Dec 20, 2019 at 10:46 AM Nethi, Manoj
wrote:
> Hi,
>
>
>
> We are seeing the following error w
Hi,
We are seeing the following error while bootstrapping a node which is
replacement of a failed node in a multi DC cluster.
WARN [STREAM-IN-/**.***.***.**] 2019-12-19 23:36:40,120 StreamSession.java:641
- [Stream #f231db30-22da-11ea-b38a-0f6cfab62953] Retrying for following error
java.lang
