You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgenii Zhuravlev (Jira)" <ji...@apache.org> on 2020/08/28 19:53:00 UTC

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

Evgenii Zhuravlev created IGNITE-13391:
------------------------------------------

             Summary: Ignite-hibernate doesn't recreate cache proxies after full reconnect to the cluster
                 Key: IGNITE-13391
                 URL: https://issues.apache.org/jira/browse/IGNITE-13391
             Project: Ignite
          Issue Type: Bug
          Components: hibernate
    Affects Versions: 2.7.6
            Reporter: Evgenii Zhuravlev


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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)