- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi Pau,
From the looks of it, it seems like FlexMatch was able to match the two tickets together, but the Queue (linked to your Matchmaking Configuration) failed to place the corresponding match onto your fleet.
A queue is configured to retry placements until the configured Queue timeout after which the tickets are transitioned to a TIMED_OUT
status. It's difficult to reason why the Queue couldn't create the placement on the fleet without looking at your specific resources, but I would check the AvailableGameSessions
metric for the particular fleet in your CloudWatch account to ensure there are active, healthy server processes which are capable of placing Game Sessions. If this is 0, it may be indicative of:
- Insufficiently scaled fleets, in which case you can scale up your fleets to always have AvailableGameSessions.
- Problems with the Game Session going ACTIVE. You can verify this by looking at game session logs on the box when SSH'd onto the host. This logs are located at
C:\Game\
for Windows (or)/local/game
for Linux.
If you need further assistance please cut GameLift a support ticket so we can help identify the exact root cause for your issue.
Thanks!
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
It would help your question if you can provide context, such as what is GameLift and FlexMatch and links to relevant guides that you're following.