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
Is your feature request related to a problem? Please describe.
At present, Open Match users need to clean up the leftover tickets by themselves, which were not used for matchmaking.
Describe the solution you'd like
A couple of ideas here.
Add paramters to CreateTicketRequest API so that users can specify the lifetime of ticket. Open Match regularly cleans up the leftover tickets according to the user-defined lifetime.
Have a new API so that users can ask Open Match to regularly clean up the leftover tickets according to the create_time in each Ticket and the lifetime which users specified through this new API
Describe alternatives you've considered
One of my customers does this clearning up by CronJob & own scripts in K8s cluster.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
I would like there to be a "LastAccessed" time so we can use a heartbeat type system. So I can say if the ticket was last checked 30+s ago I can assume they've disconnected.
Is your feature request related to a problem? Please describe.
At present, Open Match users need to clean up the leftover tickets by themselves, which were not used for matchmaking.
Describe the solution you'd like
A couple of ideas here.
Add paramters to CreateTicketRequest API so that users can specify the lifetime of ticket. Open Match regularly cleans up the leftover tickets according to the user-defined lifetime.
Have a new API so that users can ask Open Match to regularly clean up the leftover tickets according to the create_time in each Ticket and the lifetime which users specified through this new API
Describe alternatives you've considered
One of my customers does this clearning up by CronJob & own scripts in K8s cluster.
Additional context
N/A
The text was updated successfully, but these errors were encountered: