When a server process tries to acquire a port that has already been acquired by a second process I'm assuming it fails? If so, can the server backoff and retry to find the next port that is available? This might help deal with contention when multiple processes are detecting the same port as available.
Alternatively, you could pass in a static port number as a parameter to your
ServerLaunchParameters. Since you have a fixed number of processes are going to launch, each could read a different unique parameter that it can use to as the port number it will try to acquire, completely avoiding contention.
UE4+Gamelift client connection failsAccepted Answerasked a year ago
.NET 5 Server App on GameLift?Accepted Answerasked a year ago
GameLift architectureAccepted Answerasked a year ago
Server with multiple roomsasked a year ago
Running Steam-enabled servers on GameLiftasked 2 years ago
Can I run more than one game session on a single game server process?Accepted Answerasked 5 years ago
PlayerSessionIds only accepted sometimes by gamelift serverasked 3 years ago
Cannot create concurrent game sessions on spot instances in GameLift fleetasked 2 months ago
GameLift multiple processes can not detect open ports on Windows Serverasked 2 months ago
How do ports get handled when running multiple server processes per instance?Accepted Answerasked 6 years ago