Section – Redis Session Store

Specifies where the session store is located.

• Local: Use the local Redis instance as session store
• Remote server: Store all sessions in a single remote Redis instance, multiple servers can be configured, but only the first server will be considered.
• Remote cluster: Use a Redis cluster as remote session store, multiple servers can be configured. Although one entry is sufficient to connect to a Redis cluster, it is recommended to configure at least two nodes for redundancy. So Airlock Gateway is still capable of connecting to the cluster, even if one node is not available. These entries are only used to receive the cluster configuration and learn about all the cluster nodes, with which Airlock Gateway will later communicate directly.

Since the session store is an essential component for Airlock Gateway, it is very important that any remote Redis service is very responsive and highly available. Any disruption of the Redis service will greatly impair the performance and functionality of Airlock Gateway.

If enabled, Airlock Gateway will calculate the optimal session store size. Automatic sizing is only available in Local mode and is highly recommended. Otherwise consider reserving ~100KB per session that the session store should ever handle simultaneously.

Maximum amount of megabytes Airlock Gateway is allowed to use for the session store. This amount has to be available on the Redis master node respectively in the sum of all cluster master nodes.

If the above limit is reached, no new sessions may be created. But if there is not enough space available on the Redis service, the whole functionality of Airlock Gateway will be impaired. Therefore it is recommended to set the limit a few percent below the actual space available on the Redis service.