Invalid configuration file key by storagenode-updater - retain.concurrency

Since I added this in config:
retain.concurrency: 1
I get this entrie in log:

2024-06-09T21:39:18Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "retain.concurrency"}

It appears on each node update or restart among others:

2024-06-21T09:22:39Z    INFO    Configuration loaded    {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocated-bandwidth"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage2.monitor.verify-dir-writable-interval"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "retain.concurrency"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage2.monitor.verify-dir-writable-timeout"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage2.monitor.verify-dir-readable-timeout"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.private-address"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.wallet-features"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.email"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "healthcheck.details"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "console.address"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.wallet"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.address"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage2.monitor.verify-dir-readable-interval"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "contact.external-address"}
2024-06-21T09:22:39Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "healthcheck.enabled"}
2024-06-21T09:22:39Z    INFO    Anonymized tracing enabled      {"Process": "storagenode-updater"}

Now, when I grep for retain to check the BF, I get those lines too.

Don’'t worry.
The updater software reads the same config.yaml for parameters and doesn’t “understand” them because they’re not relevant to it, so throws lots of errors on startup. That one can be ignored :))

3 Likes