From a25d4385afca78db00dea994a784aed44dd740db Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Joni=20K=C3=A4h=C3=A4r=C3=A4?= Date: Tue, 28 Mar 2023 22:47:06 +0300 Subject: [PATCH] [chore] fix typo in ballast extension's README (#7431) --- extension/ballastextension/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/extension/ballastextension/README.md b/extension/ballastextension/README.md index 41b3fd0679b..a67ab0bbbca 100644 --- a/extension/ballastextension/README.md +++ b/extension/ballastextension/README.md @@ -23,7 +23,7 @@ When `size_in_percentage` is enabled with the value(1-100), the absolute `ballas 1. Look up Memory Cgroup subsystem on the target host or container, find out if there is any total memory limitation has been set for the running collector process. Check the value in `memory.limit_in_bytes` file under cgroup memory files (eg, `/sys/fs/cgroup/memory/memory.limit_in_bytes`). -2. If `memory.limit_in_bytes` is positive value other than `9223372036854771712`(`0x7FFFFFFFFFFFF000`). The `ballest_size` +2. If `memory.limit_in_bytes` is positive value other than `9223372036854771712`(`0x7FFFFFFFFFFFF000`). The `ballast_size` will be calculated by `memory.limit_in_bytes * size_in_percentage / 100`. If `memory.limit_in_bytes` value is `9223372036854771712`(`0x7FFFFFFFFFFFF000`), it indicates there is no memory limit has been set for the collector process or the running container in cgroup. Then the `totalMemory` will be determined in next step.