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/02/13 16:15:04 UTC

[jira] [Created] (IGNITE-7693) New node joining via ZookeeperDiscoverySpi should print out its ZooKeeper sessionId

Sergey Chugunov created IGNITE-7693:
---------------------------------------

             Summary: New node joining via ZookeeperDiscoverySpi should print out its ZooKeeper sessionId
                 Key: IGNITE-7693
                 URL: https://issues.apache.org/jira/browse/IGNITE-7693
             Project: Ignite
          Issue Type: Improvement
            Reporter: Sergey Chugunov


For now there is no way to match Ignite nodes joining to Ignite cluster with log entries in ZooKeeper nodes' logs.

In ZooKeeper logs there are entries like this:
{noformat}
myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x161575d88530007 with negotiated timeout 10000 for client /<host>:<port>{noformat}
but it is hard to match them with Ignite nodes when there are several started on the same host.

If Ignite node prints out its session on join it makes correlating them with particular ZooKeeper instance much easier.



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