Hi,
We’ve noticed our fleets are leaking game sessions. The issue seems to have started around the time AWS experienced outages in us-east-1
, around Nov 25th – though we’re unsure whether it’s related. We haven’t made any application code changes and we were not experiencing this issue before then. We took a quick look at some of the instances and there doesn’t seem to be any immediately obvious issues when calling processEnding
.
We have auto-scaling enabled and the fleet will eventually spin up instances until it hits the max. Our last fleet spun up ~6 instances and maintained them even when there were close to 0
player sessions at some odd hour of the night. Looking at the console, though, there were many game sessions with 0
player sessions with days of uptime.
We’ve since phased out this fleet (and continue to do so). Here’s a fleet we’ve removed from our queue with 0
player sessions, 28
dangling game sessions, and 3
active instances. Each instance is set up to allow for 35
concurrent processes – why are there 3
active instances? I was hoping a GameLift engineer might take a look at our fleet and illuminate what the problem is:
Region: us-east-1
FleetId: fleet-1188ab57-ac39-42cb-b0a1-29f4020012f4
Cheers