Hi,
I have a rather simple question for which we can't find a clear answer:
We insert all our data with a TTL of 1 month.
Do we still need to run manual regular repairs or will CG get rid of the data automatically?
thanks!
TTL and repair
(4 posts) (2 voices)- Started 3 months ago by Fransen
- Latest reply from rbranson
- This topic is resolved
-
Thank you for your answer,
We have a rather large dataset with some CF's that are close to 100GB, and have not yet run a repair on this node.
We tried to run repair, but after a week we stopped because performance was impacted.Can you tell me what would be the consequence of not repairing?
And if there is something that could speed up the repair?thanks!
Posted 3 months ago # -
There is always going to be a cost in running the anti-entropy system (repair). It's fundamentally a complex operation. If the other mechanisms (hinted handoff and read repair) do not repair data after replication failure, the consequence is that data can become synchronized between replicas. At best, this means stale data will be read for low consistency operations. At worst, it means deleted data will reappear when tombstones are cleaned up.
Posted 3 months ago # -
Thank you for your answer,
We have a rather large dataset with some CF's that are close to 100GB, and have not yet run a repair on this node. We tried to runescape gold run repair, but after a week we stopped because performance was impacted.
Can you tell me runescape accounts what would be the consequence of not repairing?
And if there is something that could speed up the repair?
thanks!Posted 2 months ago #
Reply
You must log in to post.
