SYS container gets out of sync easily

[ConanMishler]

This is an issue @walkjivefly has mentioned before, and now I'm starting to experience it with increasing regularity.
The issue is that the SYS daemon, while running inside a docker container, seems to get out of sync with the blockchain quite easily/frequently. I think it happens more frequently if the host system is under heavy load.

Notably, @walkjivefly has noticed it never happens when the SYS daemon is running outside of a docker container. It only seems to happen in our EXR ENV, where SYS daemon runs inside a docker container. This suggests the issue is related to the way SYS daemon is being run in a docker container in our EXR ENV.

The importance of this issue has recently increased significantly as we prepare to provide reliably indexed SYS NEVM data via XQuery.

[ConanMishler]

Note: I haven't seen this issue for weeks on any of the 3 servers where I'm running SYS inside a docker container. Maybe it went away? 🙏

[ConanMishler]

Update: The only way I've found to address this issue is to manually add peers by adding addnode statements to syncoin.conf which is generated in ~/exrproxy-env/scripts/entrypoints/start-syscoin.sh. I also still think the problem is exacerbated when the server on which SYS is running is heavily loaded and slow.

[ConanMishler]

In my original post on this issue, I wrote, "I think it happens more frequently if the host system is under heavy load."
Now that I have several additional data points, I can say with 99% certainty, "It definitely happens more frequently if the host system is under heavy load."