#1 Set the cassandra service to not auto-start. #2 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 <yupingwyp1...@gmail.com> 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 going from up to down and up again. The problem is when the > down node rejoins the cluster after 15 minutes, it automatically adds > already deleted data back and causing zombie data. > > our questions: > > 1. Is there a way to not allow a down node to rejoin the cluster? > 2. or is there a way to configure rejoining node not adding stale data > back regardless of how long the node is down before rejoining > 3. or is there a way to auto clean up the data when rejoining ? > > We know adding those data back is a conservative approach to avoid data > loss but in our specific case, we are not worried about deleted data being > revived.... we don’t have such use case. We really need a non-defaul option > to never add back deleted data on rejoining nodes. > > this functionality will ultimately be a deciding factor on whether we can > continue with Cassandra. > > > Thanks again, >
