You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, the same bug still manifests with GridGain Ignite 8.8.5
while using GridGain Ignite as remote Hibernate L2 cache
and same client node reconnect conditions.
When a client node disconnects from a cluster its caches are not being properly refreshed and are marked as "stopped" after reconnection.
see https://stackoverflow.com/questions/49785044/ignitecheckedexception-failed-to-perform-cache-operation-cache-is-stopped
and https://stackoverflow.com/questions/46053089/ignite-cache-reconnection-issue-cache-is-stopped
This references a fix at https://issues.apache.org/jira/browse/IGNITE-5789 and Apache Ignite 2.7+
However, the same bug still manifests with GridGain Ignite 8.8.5
while using GridGain Ignite as remote Hibernate L2 cache
and same client node reconnect conditions.
Is there any posibility of replicating the fix from https://issues.apache.org/jira/browse/IGNITE-5789 ?
The text was updated successfully, but these errors were encountered: