You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It can happen in real life situation if a client still has a reference to a deleted node.
Even if we add a check at write time, it could still happen because of concurrency issues.
What is the expected behavior?
Provide an ORPHAN_DATA check in CassandraAppStorage. It will identify the data which are linked to a non existing node.
The repair will simply delete those data.
What is the motivation / use case for changing the behavior?
Being able to identify and delete orphan data, which can waste some disk space.
The text was updated successfully, but these errors were encountered:
Feature
It's easy to create data linked to a non existing node, for example:
It can happen in real life situation if a client still has a reference to a deleted node.
Even if we add a check at write time, it could still happen because of concurrency issues.
Provide an
ORPHAN_DATA
check inCassandraAppStorage
. It will identify the data which are linked to a non existing node.The repair will simply delete those data.
Being able to identify and delete orphan data, which can waste some disk space.
The text was updated successfully, but these errors were encountered: