Commit 3dbabc5b authored by Georgios Bitzes's avatar Georgios Bitzes
Browse files

raft: reduce default trimming batch size to 200k

parent d55b9a77
Pipeline #2022128 failed with stages
in 50 minutes and 53 seconds
......@@ -19,6 +19,8 @@ for earnest only if it has a good chance of winning.
- Checkpoint creation through ``quarkdb-checkpoint`` will now fail if a different
physical filesystem is specified.
- RPMs now available for CentOS 8.
- Print explicit warnings in the log in case of write stalling.
- Reduce default trimming batch size to 200k.
Many thanks to Franck Eyraud (JRC) for the bug report concerning erroneous ``MANIFEST``-related
......@@ -15,8 +15,8 @@ journal entries. Values below 1 million are probably not reasonable for a produc
deployment, and values below 100k are disallowed.
* The batch size to use during trimming: This many entries will be deleted at once
when it's time to apply trimming. Default value is 1 million. Aim for batch sizes
around `1/50` of the total number of entries to keep.
when it's time to apply trimming. Default value is 200k. Too high batch sizes
might cause write stalls -- values higher than 1 million are not recommended.
You can change the above values with the following command towards the leader. This
sets total number of entries to keep at 10M, and batch size at 200k.
......@@ -89,7 +89,7 @@ TrimmingConfig RaftConfig::getTrimmingConfig() {
if(st.IsNotFound()) {
// Return default values
return { 50000000, 1000000 };
return { 50000000, 200000 };
else if(!st.ok()) {
qdb_throw("Error when retrieving journal trim limit: " << st.ToString());
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment