[IGNITE-13391] Ignite-hibernate doesn't recreate cache proxies after full reconnect to the cluster

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.7.6
• Component/s: hibernate
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Evgenii Zhuravlev
• Created: 28/Aug/20 19:52
• Updated: 28/Aug/20 19:52

Description

If there is only one server node in the cluster and user restart it, client node reconnects to the completely new cluster and, in order to continue using the ignite-hibernate integration, it should recreate all the cache proxies. Otherwise, it leads to the issue described in this thread:
http://apache-ignite-users.70518.x6.nabble.com/Hibernate-2nd-Level-query-cache-with-Ignite-td33816.html

We should add proxies reinitialization on reconnect.