Understanding and tuning RH-SSO distributed caches ?

Issue

Within RH-SSO 7.6 standalone-ha.xml, the distributed caches are configured as follows:

 <distributed-cache name="sessions" owners="1">
                    <expiration lifespan="900000000000000000"/>
                </distributed-cache>
                <distributed-cache name="authenticationSessions" owners="1">
                    <expiration lifespan="900000000000000000"/>
                </distributed-cache>
                <distributed-cache name="offlineSessions" owners="1">
                    <expiration lifespan="900000000000000000"/>
                </distributed-cache>
                <distributed-cache name="clientSessions" owners="1">
                    <expiration lifespan="900000000000000000"/>
                </distributed-cache>
                <distributed-cache name="offlineClientSessions" owners="1">
                    <expiration lifespan="900000000000000000"/>
                </distributed-cache>
                <distributed-cache name="loginFailures" owners="1">
                    <expiration lifespan="900000000000000000"/>
                </distributed-cache>
                <distributed-cache name="actionTokens" owners="2">
                    <heap-memory size="-1"/>
                    <expiration interval="300000" lifespan="900000000000000000" max-idle="-1"/>
                </distributed-cache>

As a result the caches with owners="1" will cause loss of data, i.e. clientSession, in case of a RH-SSO cluster of 2 or more nodes and a shutdown or failure of one node.
How is it possible to harden RH-SSO high availability ?