Understand maintenance service middleware reassignment

In an environment that has multiple middleware hosts, if the middleware that is currently handling the maintenance services goes offline for some reason, the system waits for a predefined amount of time before another middleware is assigned to handle those services. This allows the original middleware to resume handling the services in case the issue is temporary. However, if this time interval is exceeded, then another middleware is assigned to take over these services.

The time interval is defined by the wait_time_before_takeover value in the db_status table. The default is 2 minutes, which is also the minimum value, but this value can be changed by updating the table.

The following diagram illustrates how this reassignment is handled, assuming that the wait time is set to 10 minutes.