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
With the introduction of the new EU region for A3, traffic has the random chance of being routed from A3 to A1 or A2 if the statefulset is within these regions. This works, but introduces latency.
Two new records have been added.
na.mcserverhosting.net
eu.mcserverhosting.net
These records should correspond with the assigned SRV of the deployment. Nodes have been labeled with region=ca and regoin=eu for the proper nodes. This should go in tandem with work to synchronize DNS records w/ a source -- mcserverhosting-net/cluster#1
Applying the routing this way vs using HostPort + assignment would ensure no interrupts upon move while also eventually reducing the travel time between the client and the node of the hosted statefulset.
The text was updated successfully, but these errors were encountered:
With the introduction of the new EU region for A3, traffic has the random chance of being routed from A3 to A1 or A2 if the statefulset is within these regions. This works, but introduces latency.
Two new records have been added.
na.mcserverhosting.net
eu.mcserverhosting.net
These records should correspond with the assigned SRV of the deployment. Nodes have been labeled with
region=ca
andregoin=eu
for the proper nodes. This should go in tandem with work to synchronize DNS records w/ a source -- mcserverhosting-net/cluster#1Applying the routing this way vs using HostPort + assignment would ensure no interrupts upon move while also eventually reducing the travel time between the client and the node of the hosted statefulset.
The text was updated successfully, but these errors were encountered: