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
But base on the Health Failure Strategy 1. If any of the GameServer container fails exits before the GameServer moves to Ready then, it is restart as per the restartPolicy (which defaults to “Always”)
I didn't change the restartPolicy and gameserver describe events part didnt print SDK.Ready() complete why the game server didn't restart and only the gameserver in fleet will restart?
Ah, that is a legitimate documentation bug! Nice find! 👍
It should read: If any of the GameServer container exits with an error before the GameServer moves to Ready then, the game server container is restarted as per the restartPolicy (which defaults to “Always”)
And it should also state if the GameServer health check fails at any point, the GameServer is moved to Unhealthy. We should also have a section in here on what happens with Fleets in GameServers when they move to Unhealthy -- which is they get deleted (not restarted, like above), and then recreated. Which is the difference you are seeing.
There was an erroneous statement in the documentation on how health
checking and process exit would impact if a GameServer would become
Unhealthy. This commit fixes this issue.
This also adds a section on how Unhealthy GameServers are handled when
in a Fleet vs when there are individually created.
Closesgoogleforgames#1229
There was an erroneous statement in the documentation on how health
checking and process exit would impact if a GameServer would become
Unhealthy. This commit fixes this issue.
This also adds a section on how Unhealthy GameServers are handled when
in a Fleet vs when there are individually created.
Closesgoogleforgames#1229
There was an erroneous statement in the documentation on how health
checking and process exit would impact if a GameServer would become
Unhealthy. This commit fixes this issue.
This also adds a section on how Unhealthy GameServers are handled when
in a Fleet vs when there are individually created.
Closes#1229
There was an erroneous statement in the documentation on how health
checking and process exit would impact if a GameServer would become
Unhealthy. This commit fixes this issue.
This also adds a section on how Unhealthy GameServers are handled when
in a Fleet vs when there are individually created.
Closesgoogleforgames#1229
Ah, that is a legitimate documentation bug! Nice find! 👍
It should read:
If any of the GameServer container exits with an error before the GameServer moves to Ready then, the game server container is restarted as per the restartPolicy (which defaults to “Always”)
And it should also state
if the GameServer health check fails at any point, the GameServer is moved to Unhealthy
. We should also have a section in here on what happens with Fleets in GameServers when they move to Unhealthy -- which is they get deleted (not restarted, like above), and then recreated. Which is the difference you are seeing.Originally posted by @markmandel in #1217 (comment)
/assign @markmandel
The text was updated successfully, but these errors were encountered: