Closed jterrier84 closed 3 years ago
After restarting the docker container, the MAX_PEERS variable was loaded into the topologyUpdater file.
I verified that -e MAX_PEERS=6
works as expected and results in a topology update request with the corresponding parameter. However, I also observe this https://github.com/cardano-community/guild-operators/issues/1082
Note, the topology file is NOT dynamically reloaded. Instead it requires a restart of the node or in our case a restart of the container. For the topology to survive a restart, it must be written to a persistent volume.
Leaving open for now.
This should be fixed now (on their end)
Actual situation The environment variable MAX_PEERS can not be edited. It seems that it gets overwritten to a fixed value =15 in the topologyUpdate script.
New situation Make the MAX_PEERS variable configurable from outside the container.