summaryrefslogtreecommitdiffstats
path: root/searchcore
diff options
context:
space:
mode:
authorGeir Storli <geirst@verizonmedia.com>2019-09-17 10:43:02 +0000
committerGeir Storli <geirst@verizonmedia.com>2019-09-17 10:43:02 +0000
commitdd12202a57496cbe8f16fd1697518dec5bc5be6b (patch)
tree96d8adf89b91c5052f92dc80024279ea2b55c6c6 /searchcore
parente183263842a92f905745aed3b7e53c9bae4def1f (diff)
Adjust defaults for lid space compaction job.
Run check for lid space compaction more frequently and reduce time for when to consider a remove batch operation as ongoing.
Diffstat (limited to 'searchcore')
-rw-r--r--searchcore/src/vespa/searchcore/config/proton.def6
1 files changed, 3 insertions, 3 deletions
diff --git a/searchcore/src/vespa/searchcore/config/proton.def b/searchcore/src/vespa/searchcore/config/proton.def
index fd50dd2094a..deec60dbf50 100644
--- a/searchcore/src/vespa/searchcore/config/proton.def
+++ b/searchcore/src/vespa/searchcore/config/proton.def
@@ -341,8 +341,8 @@ packetcompresstype enum {NONE, LZ4} default=LZ4
## Interval between considering if lid space compaction should be done (in seconds).
##
-## Default value is 10 minutes (600 seconds).
-lidspacecompaction.interval double default=600.0
+## Default value is 10 seconds.
+lidspacecompaction.interval double default=10.0
## The allowed lid bloat (in docs) before considering lid space compaction.
##
@@ -364,7 +364,7 @@ lidspacecompaction.allowedlidbloatfactor double default=0.01
## Remove batch operations are used when deleting buckets on a content node.
## This functionality ensures that during massive deleting of buckets (e.g. as part of redistribution of data to a new node),
## lid space compaction do not interfere, but instead is applied after deleting of buckets is complete.
-lidspacecompaction.removebatchblockdelay double default=5.0
+lidspacecompaction.removebatchblockdelay double default=2.0
## This is the maximum value visibilitydelay you can have.
## A to higher value here will cost more memory while not improving too much.