You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a whitelist for dmsg clients of a dmsg server. Like reserved spots.
So if I'm running a dmsg server and suddenly all the other dmsg servers go down and my dmsg server hits its connection limit, it would always leave open slots for certain dmsg clients to connect there (i.e. visors i am running, etc.).
When this is implemented we need to whitelist all the deployment services including setup-node for all dmsg servers.
And we should suggest that anyone who runs a dmsg server to the dmsg discovery on prod also whitelists the deployment services.
So that in the event of dmsg instability or servers going down unexpectedly, the deployment services would be able to connect to any dmsg server, even if it had hit its connection limit because of reserved spots.
The text was updated successfully, but these errors were encountered:
We need a whitelist for dmsg clients of a dmsg server. Like reserved spots.
So if I'm running a dmsg server and suddenly all the other dmsg servers go down and my dmsg server hits its connection limit, it would always leave open slots for certain dmsg clients to connect there (i.e. visors i am running, etc.).
When this is implemented we need to whitelist all the deployment services including setup-node for all dmsg servers.
And we should suggest that anyone who runs a dmsg server to the dmsg discovery on prod also whitelists the deployment services.
So that in the event of dmsg instability or servers going down unexpectedly, the deployment services would be able to connect to any dmsg server, even if it had hit its connection limit because of reserved spots.
The text was updated successfully, but these errors were encountered: