You should limit the duration of an active HTTP session for a maximum of 10 minutes, even if the HTTP session continuously performs transactions. Determining the maximum duration that a session should be held open is a trade‐off between the benefits of session persistence and the ideal allocation of the session to internal system resources.
Limited HTTP sessions provide the following benefits:
To optimize load balancing across the StorageGRID Webscale system, you should prevent long‐lived TCP/IP sessions. You should configure client applications to track the duration of each HTTP session and close the HTTP session after a set time so that the HTTP session can be reestablished and rebalanced.
The StorageGRID Webscale system balances its load when a client application establishes an HTTP session. Over time, an HTTP session that the StorageGRID Webscale system uses for a compute resource might no longer be optimal as load balancing requirements change. The system performs its best load balancing when client applications establish a separate HTTP session for each transaction, but this negates the much more valuable gains associated with persistent sessions.
Some maintenance procedures start only after all the in-progress HTTP sessions are complete.