Posted: 3 Oct 2018 7:40 EDT Last activity: 21 Mar 2019 12:13 EDT
ADM CommitLog in Cassandra/DNode sizing
we've recently implemented more modems in our DSM implementation. We're seeing an increase in growth in cassandra (/cassandra_data was 35 GB). Are there tuning parameters to flush this data to the DB? We're going to be applying the hotfix for 42009 for the OperationTimedOut exception on node start/sync. The commitlog table itself is 12 GB and that query is timing out.
***Edited by Moderator Marissa to update SR Details***
it's the adm_response_commitlog within cassandra (so a Pega table/keyspace) that was timing out. There was a hotfix to apply. I also posted another question around gc_grace_seconds to see about reclaiming disk space more frequently than 10 days.