Unsubscribe
> On May 20, 2024, at 11:26 AM, Brandon Williams
> wrote:
>
> The Cassandra team is pleased to announce the release of Apache
> Cassandra version 4.0.13.
>
> Apache Cassandra is a fully distributed database. It is the right
> choice when you need scalability and high availability w
That's what nodetool assassinte will do.
On Sun, Apr 2, 2023 at 10:19 PM David Tinker wrote:
> Is it possible for me to remove the node from the cluster i.e. to undo
> this mess and get the cluster operating again?
>
> On Mon, Apr 3, 2023 at 7:13 AM Carlos Diaz wrote:
>
&g
false.
>
> Thanks very much for the help.
>
>
> On Mon, Apr 3, 2023 at 7:01 AM Carlos Diaz wrote:
>
>> Just remove it from the seed list in the cassandra.yaml file and restart
>> the node. Make sure that auto_bootstrap is set to true first though.
>>
>> On S
ries.
>>
>> I did make the new node a seed node.
>>
>> Re "rack4": I assumed that was just an indication as to the physical
>> location of the server for redundancy. This one is separate from the others
>> so I used rack4.
>>
>> On Mon, Apr 3,
I'm assuming that your replication factor is 3. If that's the case, did
you intentionally put this node in rack 4? Typically, you want to add
nodes in multiples of your replication factor in order to keep the "racks"
balanced. In other words, this node should have been added to rack 1, 2 or
3.
Hi Team,
We are heavy users of Cassandra at a pretty big bank. Security measures
require us to constantly refresh our C* nodes every x number of days. We
normally do this in a rolling fashion, taking one node down at a time and
then refreshing it with a new instance. This process has been worki
