Details
-
Bug
-
Resolution: Fixed
-
Major
-
Cheshire-Cat
-
Centos 7 64 bit; CB EE 7.0.0-4936
-
Untriaged
-
Centos 64-bit
-
-
1
-
No
Description
Summary:
I accidentally set the pruningInterval to a low number(=1) mistaking the unit of the pruningInterval to be minutes (which in actual is milliseconds).
But after doing the above, within seconds the error logs, info logs, babysitter logs got flooded with many entries like below:
[ns_server:error,2021-04-14T00:30:01.865-07:00,ns_1@172.23.105.215:prometheus_cfg<0.365.0>:prometheus_cfg:handle_info:487]Received exit from pruning pid <0.13732.1> with reason {{badmatch,[]},
|
[{prometheus_cfg,
|
build_decimation_summary,
|
1,
|
[{file,
|
"src/prometheus_cfg.erl"},
|
{line,1410}]},
|
{prometheus_cfg,
|
report_decimation_summary,
|
1,
|
[{file,
|
"src/prometheus_cfg.erl"},
|
{line,1392}]},
|
{prometheus_cfg,
|
run_decimate_stats,
|
2,
|
[{file,
|
"src/prometheus_cfg.erl"},
|
{line,1376}]},
|
{prometheus_cfg,
|
run_prune_stats,2,
|
[{file,
|
"src/prometheus_cfg.erl"},
|
{line,1337}]},
|
{proc_lib,init_p,3,
|
[{file,
|
"proc_lib.erl"},
|
{line,234}]}]}.
|
logs are flooded with the above (or similar) message.
So assigning to ns-server if anything is of concern here.