[
https://issues.apache.org/jira/browse/IGNITE-7693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363415#comment-16363415
]
Roman Shtykh commented on IGNITE-7693:
--------------------------------------
[~sergey-chugunov] Please have a look. Probably still not the best way to see
session id in the logs, but at least now you can have these lines in your node
logs.
{noformat}
[TcpDiscoveryZookeeperIpFinder] Connected with session id: 0x2619230f8d00000
...
[TcpDiscoveryZookeeperIpFinder] Registering addresses with ZooKeeper IP Finder:
[/127.0.0.1:47500]{noformat}
> 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
(v7.6.3#76005)
