summaryrefslogtreecommitdiffstats
path: root/searchcore
diff options
context:
space:
mode:
authorHenning Baldersheim <balder@yahoo-inc.com>2022-04-25 17:25:10 +0200
committerGitHub <noreply@github.com>2022-04-25 17:25:10 +0200
commit162aee0256a8b22ce29304ac0ce073a2572880e1 (patch)
treeabe1134ae48b13b22c5b6a3e4a463db22ccc51ba /searchcore
parent03635338d6553dd122fe273c102bcb1097adb15a (diff)
Update searchcore/src/vespa/searchcore/proton/server/disk_mem_usage_sampler.cpp
Co-authored-by: Geir Storli <geirst@yahooinc.com>
Diffstat (limited to 'searchcore')
-rw-r--r--searchcore/src/vespa/searchcore/proton/server/disk_mem_usage_sampler.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/searchcore/src/vespa/searchcore/proton/server/disk_mem_usage_sampler.cpp b/searchcore/src/vespa/searchcore/proton/server/disk_mem_usage_sampler.cpp
index fceebefa0fc..8f3d9603821 100644
--- a/searchcore/src/vespa/searchcore/proton/server/disk_mem_usage_sampler.cpp
+++ b/searchcore/src/vespa/searchcore/proton/server/disk_mem_usage_sampler.cpp
@@ -50,7 +50,7 @@ void
DiskMemUsageSampler::sampleAndReportUsage()
{
TransientResourceUsage transientUsage = sample_transient_resource_usage();
- /* It is important that transient memory is reported first. This prevents
+ /* It is important that transient resource usage is sampled first. This prevents
* a false positive where we report a too high disk or memory usage causing
* either feed blocked, or an alert due to metric spike.
* A false negative is less of a problem, as it will only be a short drop in the metric,