Is there workaround to shorten 72 hours to something shorter?(you said by
default, wondering if one can set a non-default value?)
Thanks,
Yuping
On Jul 29, 2019, at 7:28 AM, Oleksandr Shulgin
wrote:
> On Mon, Jul 29, 2019 at 1:21 PM Rahul Reddy wrote:
>
> Decommissioned 2 nodes from clust
We have the same issue. We observed the JMX only cleared after exactly 72 hours
too.
On Jul 29, 2019, at 11:23 AM, Rahul Reddy wrote:
And also system.peers table doesn't have the information on old nodes only
ghost nodes to be there in JMX
> On Mon, Jul 29, 2019, 7:39 AM Rahul Reddy wrote:
Longer gc_grace time would help
#3 Rebootstrap?
If the node doesn't come back within gc_grace,_seconds, remove the node, wipe
it, and bootstrap it again.
https://docs.datastax.com/en/archived/cassandra/2.0/cassandra/dml/dml_about_deletes_c.html
yuping wang schrieb am Mo., 1. Juli 2019, 13:33:
Hi all,
Sorry for the interruption. But I need help.
Due to specific reasons of our use case, we have gc grace on the order of
10 minutes instead of default 10 days. Since we have a large amount of nodes in
our Cassandra fleet, not surprisingly, we encounter occasionally node status
go
