Online docs has incorrect JVM flag unsafe_aggressive_sstable_expiration for TimeWindowCompactionStrategy
-2
votes
1
answer
22
views
I was installing the unsafe_aggressive_sstable_expiration and found out that there is a mistake in the documentation. The documentation told us that we needed to enable in the jvm -Dcassandra.unsafe_aggressive_sstable_expiration=true, while we actually needed to use -Dcassandra.**allow_**unsafe_aggressive_sstable_expiration=true. I think it is important that this gets fixed because this can led the users to some time loss until they find out the issue.
Adding to that, it would be great if you could add some documentation on the procedure to install these tags. For instance, we did not know if these tags needed to be in the cassandra.yaml file or if they had to be in the env-sh file. It was in the second that they needed to be installed, and this led us to some time loss as well.
Thanks for your attention
Asked by Jon Corral
(1 rep)
Jul 4, 2024, 12:43 PM
Last activity: Aug 1, 2024, 03:24 AM
Last activity: Aug 1, 2024, 03:24 AM