-
Notifications
You must be signed in to change notification settings - Fork 829
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ports should always be allocated to a GameServer #415
Ports should always be allocated to a GameServer #415
Conversation
The allocator was written before we have the autoscaler, which has a requirement to be able to start GameServers past the current number of nodes, so that the autoscaler can find room for them automaticaly. The previous port allocator would only allow port ranges for each current node - but this PR will allow it to go past that, and dynamically add port ranges as required. This also removes the requirement to do a full `GameServer` port sync every time a Node gets removed, and drops a somewhat lengthy locking process.
Build Succeeded 👏 Build Id: 8791a01e-e4eb-4284-b531-914d5b99b7ec The following development artifacts have been built, and will exist for the next 30 days:
(experimental) To install this version:
|
Build Failed 😱 Build Id: 133a7fb1-26d4-457c-b18f-e9255b871d0a Build Logs
|
Build Succeeded 👏 Build Id: 6fdf0dda-cfeb-458c-9b25-3aa5191ee842 The following development artifacts have been built, and will exist for the next 30 days:
(experimental) To install this version:
|
The allocator was written before we have the autoscaler, which has a requirement to be able to start GameServers past the current number of nodes, so that the autoscaler can find room for them automaticaly.
The previous port allocator would only allow port ranges for each current node - but this PR will allow it to go past that, and dynamically add port ranges as required.
This also removes the requirement to do a full
GameServer
port sync every time a Node gets removed, and drops a somewhat lengthy locking process.