You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Sergey Chugunov (JIRA)" <ji...@apache.org> on 2018/06/22 13:39:00 UTC

[jira] [Created] (IGNITE-8857) ZookeeperClusterNode class instances sneak into BaselineTopology when non-empty user attributes are defined

Sergey Chugunov created IGNITE-8857:
---------------------------------------

             Summary: ZookeeperClusterNode class instances sneak into BaselineTopology when non-empty user attributes are defined
                 Key: IGNITE-8857
                 URL: https://issues.apache.org/jira/browse/IGNITE-8857
             Project: Ignite
          Issue Type: Bug
            Reporter: Sergey Chugunov
            Assignee: Sergey Chugunov


When persistence-enabled cluster is activated for the first time, it saves information about cluster nodes into BaselineTopology, including user attributes.

It turned out that in case of cluster started with ZookeeperDiscoverySpi on first activation instances of ZookeeperClusterNode are persisted to disk within BaselineTopology.
After that the same nodes cannot be switched to TcpDiscoverySpi without having ignite-zookeeper.jar on classpath.

We should prevent ZookeeperClusterNode instances to be persisted to disk.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)