Re: Streaming Failed during bootstrap of a Replacement node

Without getting too in the weeds here - ideally yes, you'd be able to replace the node. However, the error you're getting looks (at a glance) to be one of the many range tombstone bugs that were fixed in later versions. On Fri, Dec 20, 2019 at 11:23 AM Nethi, Manoj wrote: > Hi Jon, > > Yes we w

RE: Streaming Failed during bootstrap of a Replacement node

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 email

Re: Streaming Failed during bootstrap of a Replacement node

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

Streaming Failed during bootstrap of a Replacement node

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

RE: Data is not syncing up when we add one more Node(DR) to existing 3 node cluster

Hi John, Yes! Regards, Anil Ganipineni Adaequare GSP GSP Support : 040 660 335 88 Personal : +91 96522 314 80 P Please consider environment before printing this page. From: John Belliveau Sent: 13 December 2019 06:31 To: user@cassandra.apache.org Subject: Re: D