Skip to content

Maybe adjust default value of the -m argument for easier upgrade experience #6472

@shinrich

Description

@shinrich

Due to changes in commit cba8b22, the compile time constant for maxRecords is changed to a runtime constant. The compile time constant was 2500. The default (and minimum) size with the argument is 1600. When we upgraded to 9.0, we got the following message every minute or so in diags.log

[Sep 25 21:00:46.121] [ET_NET 16] WARNING: too many stats/configs, please increase max_records_entries using the --maxRecords command line option

We fixed this by adding the -m 2500 option to our systemd service file.

However, for a superior out of the box experience on upgrade, shouldn't the new default be the same as the old compile time constant?

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions