ASF GitHub Bot commented on IGNITE-7693:

GitHub user shroman opened a pull request:


    IGNITE-7693: Printing out session ids on joining via ZookeeperDiscove…


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shroman/ignite IGNITE-7693

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3519
commit fce93839db7ddc303ca5ced3cb71e6603d4b1adc
Author: shroman <rshtykh@...>
Date:   2018-02-14T02:50:29Z

    IGNITE-7693: Printing out session ids on joining via ZookeeperDiscoverySpi.


> 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
>            Priority: Major
>             Fix For: 2.5
> 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

Reply via email to