Rethinking Server Allocation: The Reservation Approach

In the dynamic world of online gaming, efficiently connecting players to game servers is paramount. Multiplay Hosting offers a reservation system designed to optimize this process, notably for games that favor direct server selection over conventional matchmaking.

Unlike conventional allocation methods, this system empowers players to choose the specific game server they want to join, offering greater control and potentially enhancing the overall gaming experience. This approach contrasts with matchmaking systems, which automatically group players based on various criteria.

The reservation system is particularly well-suited for games where player choice and server-specific experiences are valued. For example, in simulation games or open-world environments, players might prefer to select a server based on its community, geographical location, or specific in-game events.

Active Build Configuration: Ensuring Server Consistency

A key aspect of Multiplay Hosting’s reservation system is the concept of an active build configuration. This ensures that each game server within a fleet operates with a consistent software version and settings.

Unlike allocation-based systems that might allow for multiple build configurations, the reservation system focuses on a single, active configuration for each fleet. This simplifies management and ensures a uniform experience for players joining different servers within the same fleet.

To manage and update the active build configuration, developers interact with the Multiplay Hosting API. This allows them to deploy new versions of their game server software and manage server updates efficiently.

Graceful Transitions: Managing Build Configuration Updates

When updating the active build configuration,Multiplay Hosting provides a mechanism for managing the transition process,using a graceful flag to control how servers are updated.

This flag determines how the system interacts with existing game servers when switching to a new build configuration. The update process involves a timeout period, during which Multiplay Hosting distributes the new build configuration to each server in the fleet.

the system then attempts to terminate existing servers to apply the new configuration. The behavior during this termination phase is dictated by the graceful flag:

• Graceful = True: The processor sends a SIGTERM signal to each server, allowing it to complete its current tasks before shutting down. This ensures a smooth transition and prevents data loss.
• Graceful = False: The processor waits for the server to become idle before sending a SIGKILL signal, forcing an immediate shutdown and restart with the new build configuration. This approach is faster but may result in data loss if servers are not properly prepared for termination.

The choice between these two options depends on the specific requirements of the game and the importance of minimizing downtime versus preventing data loss.

Step-by-Step Build Configuration Update

The process of updating the active build configuration can be broken down into the following steps:

1. The active build configuration of the fleet is updated with a specified timeout.
2. Multiplay hosting delivers the new build configuration to each server in the fleet.
3. The Multiplay Hosting processor attempts to terminate existing servers to apply the new active build configuration.
   • If Graceful is set to true, a SIGTERM signal is sent, allowing the server to complete its tasks before terminating.
   • If Graceful is set to false, the system waits for the server to become idle before sending a SIGKILL signal, forcing an immediate restart.