[jira] [Updated] (ZOOKEEPER-2867) an expired ZK session can be re-established
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated ZOOKEEPER-2867:
---
Attachment: 0.parsed_commit_log
1.parsed_commit_log
2.parsed_commit_log
[~hanm], attached please find the parsed commit log from ZK server 0, 1 and 2.
If you grep for close on session 0x25cd1e82c110001, you will see it in broker 1
and 2's commit log, but not on broker 0. Note that the timestamp in the commit
log is PDT, which is 7 hours ahead of UTC time. All the log4j logs in this jira
are using UTC time.
> an expired ZK session can be re-established
> ---
>
> Key: ZOOKEEPER-2867
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2867
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.10
>Reporter: Jun Rao
> Attachments: 0.parsed_commit_log, 1.parsed_commit_log,
> 2.parsed_commit_log, zk.0.08-02, zk.0.08-02, zk.0.formatted, zk.1.08-02,
> zk.1.08-02, zk.1.formatted, zk.2.08-02, zk.2.08-02
>
>
> Not sure if this is a real bug, but I found an instance when a ZK client
> seems to be able to renew a session already expired by the ZK server.
> From ZK server log, session 25cd1e82c110001 was expired at 22:04:39.
> {code:java}
> June 27th 2017, 22:04:39.000 INFO
> org.apache.zookeeper.server.ZooKeeperServer Expiring session
> 0x25cd1e82c110001, timeout of 12000ms exceeded
> June 27th 2017, 22:04:39.001 DEBUG
> org.apache.zookeeper.server.quorum.Leader Proposing::
> sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
> txntype:-11 reqpath:n/a
> June 27th 2017, 22:04:39.001 INFO
> org.apache.zookeeper.server.PrepRequestProcessorProcessed session
> termination for sessionid: 0x25cd1e82c110001
> June 27th 2017, 22:04:39.001 DEBUG
> org.apache.zookeeper.server.quorum.CommitProcessor Processing request::
> sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
> txntype:-11 reqpath:n/a
> June 27th 2017, 22:05:20.324 INFO
> org.apache.zookeeper.server.quorum.Learner Revalidating client:
> 0x25cd1e82c110001
> June 27th 2017, 22:05:20.324 INFO
> org.apache.zookeeper.server.ZooKeeperServer Client attempting to renew
> session 0x25cd1e82c110001 at /100.96.5.6:47618
> June 27th 2017, 22:05:20.325 INFO
> org.apache.zookeeper.server.ZooKeeperServer Established session
> 0x25cd1e82c110001 with negotiated timeout 12000 for client /100.96.5.6:47618
> {code}
> From ZK client's log, it was able to renew the expired session on 22:05:20.
> {code:java}
> June 27th 2017, 22:05:18.590 INFOorg.apache.zookeeper.ClientCnxn Client
> session timed out, have not heard from server in 4485ms for sessionid
> 0x25cd1e82c110001, closing socket connection and attempting reconnect 0
> June 27th 2017, 22:05:18.590 WARNorg.apache.zookeeper.ClientCnxn Client
> session timed out, have not heard from server in 4485ms for sessionid
> 0x25cd1e82c110001 0
> June 27th 2017, 22:05:19.325 WARNorg.apache.zookeeper.ClientCnxn SASL
> configuration failed: javax.security.auth.login.LoginException: No JAAS
> configuration section named 'Client' was found in specified JAAS
> configuration file: '/opt/confluent/etc/kafka/server_jaas.conf'. Will
> continue connection to Zookeeper server without SASL authentication, if
> Zookeeper server allows it. 0
> June 27th 2017, 22:05:19.326 INFOorg.apache.zookeeper.ClientCnxn Opening
> socket connection to server 100.65.188.168/100.65.188.168:2181 0
> June 27th 2017, 22:05:20.324 INFOorg.apache.zookeeper.ClientCnxn Socket
> connection established to 100.65.188.168/100.65.188.168:2181, initiating
> session 0
> June 27th 2017, 22:05:20.327 INFOorg.apache.zookeeper.ClientCnxn Session
> establishment complete on server 100.65.188.168/100.65.188.168:2181,
> sessionid = 0x25cd1e82c110001, negotiated timeout = 12000 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ZOOKEEPER-2867) an expired ZK session can be re-established
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated ZOOKEEPER-2867:
---
Attachment: zk.2.08-02
zk.0.08-02
zk.1.08-02
[~hanm], I found some additional info on Jun. 27. I actually do see session
25cd1e82c110001 being closed in the commit log on 2 of the 3 ZK servers.
First, I saw the following on ZK server 1's log4j log. It appears that it first
expired session 25cd1e82c110001. Then there was some ZK leader election,
potentially due to a network issue. Finally, it allowed a client to renew
session 25cd1e82c110001.
{code:java}
ZK 1 :
June 27th 2017, 22:04:39.000 org.apache.zookeeper.server.ZooKeeperServer
Expiring session 0x25cd1e82c110001, timeout of 12000ms exceeded
June 27th 2017, 22:04:39.001
org.apache.zookeeper.server.quorum.CommitProcessor Processing request::
sessionid:0x25cd1e82c110008 type:closeSession cxid:0x0 zxid:0x20fc5
txntype:-11 reqpath:n/a
June 27th 2017, 22:04:39.001
org.apache.zookeeper.server.quorum.CommitProcessor Processing request::
sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
txntype:-11 reqpath:n/a
June 27th 2017, 22:04:39.001 org.apache.zookeeper.server.quorum.Leader
Proposing:: sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0
zxid:0x20fc4 txntype:-11 reqpath:n/a
June 27th 2017, 22:04:39.001 org.apache.zookeeper.server.quorum.Leader
Proposing:: sessionid:0x25cd1e82c110008 type:closeSession cxid:0x0
zxid:0x20fc5 txntype:-11 reqpath:n/a
June 27th 2017, 22:04:39.001 org.apache.zookeeper.server.PrepRequestProcessor
Processed session termination for sessionid: 0x25cd1e82c110008
June 27th 2017, 22:04:39.001 org.apache.zookeeper.server.PrepRequestProcessor
Processed session termination for sessionid: 0x25cd1e82c110001
...
June 27th 2017, 22:04:42.064 org.apache.zookeeper.server.quorum.QuorumPeer
LOOKING
...
June 27th 2017, 22:04:45.824 org.apache.zookeeper.server.quorum.Learner
FOLLOWING - LEADER ELECTION TOOK - 3760
...
June 27th 2017, 22:05:20.324 org.apache.zookeeper.server.ZooKeeperServer
Client attempting to renew session 0x25cd1e82c110001 at /100.96.5.6:47618
June 27th 2017, 22:05:20.324 org.apache.zookeeper.server.quorum.Learner
Revalidating client: 0x25cd1e82c110001
June 27th 2017, 22:05:20.324 org.apache.zookeeper.server.ZooKeeperServer
Session establishment request from client /100.96.5.6:47618 client's lastZxid
is 0x203af
June 27th 2017, 22:05:20.325 org.apache.zookeeper.server.ZooKeeperServer
Established session 0x25cd1e82c110001 with negotiated timeout 12000 for client
/100.96.5.6:47618
{code}
In ZK server 1's commit log, I saw the following, which indicates that session
25cd1e82c110001 was closed.
{code:java}
6/27/17 22:04:39 session 0x25cd1e82c110001 cxid 0x0 zxid 0x20fc4
closeSession null
{code}
I saw the same session close in ZK server 2's commit log.
{code:java}
6/27/17 22:04:39 session 0x25cd1e82c110001 cxid 0x0 zxid 0x20fc4
closeSession null
{code}
However, I don't see the same session close in ZK server 0's commit log.
Also, in ZK server 2 and 0's log4j log, there was no logging for session
25cd1e82c110001 from 22:04:39.000 (when server 1 expired the session) to
22:05:20.325 (when server 1 renewed the session).
So, my questions are
(1) Does the presence of closeSession indicate that session 25cd1e82c110001 was
indeed expired on 6/27/17 22:04:39?
(2) Why the closeSession for 25cd1e82c110001 didn't show up in the commit log
of ZK server 0?
I am also attaching the log around that time in case you need them. Thanks.
> an expired ZK session can be re-established
> ---
>
> Key: ZOOKEEPER-2867
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2867
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.10
>Reporter: Jun Rao
> Attachments: zk.0.08-02, zk.0.08-02, zk.0.formatted, zk.1.08-02,
> zk.1.08-02, zk.1.formatted, zk.2.08-02, zk.2.08-02
>
>
> Not sure if this is a real bug, but I found an instance when a ZK client
> seems to be able to renew a session already expired by the ZK server.
> From ZK server log, session 25cd1e82c110001 was expired at 22:04:39.
> {code:java}
> June 27th 2017, 22:04:39.000 INFO
> org.apache.zookeeper.server.ZooKeeperServer Expiring session
> 0x25cd1e82c110001, timeout of 12000ms exceeded
> June 27th 2017, 22:04:39.001 DEBUG
> org.apache.zookeeper.server.quorum.Leader Proposing::
> sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
> txntype:-11 reqpath:n/a
> June 27th 2017, 22:04:39.001 INFO
> org.apache.zookeeper.server.PrepRequestProcessorProcessed session
> termination for sessionid: 0x25cd1e82c110001
> June 27th 2017, 22:04:39.001 DEBUG
> org.apache.zookeeper.server.quoru
[jira] [Updated] (ZOOKEEPER-2867) an expired ZK session can be re-established
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated ZOOKEEPER-2867:
---
Attachment: zk.2.08-02
zk.0.08-02
zk.1.08-02
[~hanm], I am attaching the log from 3 ZK servers on Aug. 2. What happened was
the following.
1. All 3 ZK servers went down around 23:16 and were restarted around 23:41.
2. Kafka controller, which never went down during that window, was able to
re-establish its ZK session around 23:41:58.
{code:java}
August 2nd 2017, 23:41:58.499 INFOorg.apache.zookeeper.ClientCnxn Socket
connection established to
zookeeper-2.cp14.svc.cluster.local/100.71.124.93:2181, initiating session
{code}
3. Kafka broker 0 (non-controller) went down on 23:17:18 and was restarted on
23:42:12.
Supposedly, the old ZK session for broker 0 (25cd1e82c110001) should be expired
after the ZK servers were restarted (but it didn't seem to happen). When will
the clock for session expiration starts when the ZK cluster was restarted?
After the ZK cluster has elected a leader?
> an expired ZK session can be re-established
> ---
>
> Key: ZOOKEEPER-2867
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2867
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.10
>Reporter: Jun Rao
> Attachments: zk.0.08-02, zk.0.formatted, zk.1.08-02, zk.1.formatted,
> zk.2.08-02
>
>
> Not sure if this is a real bug, but I found an instance when a ZK client
> seems to be able to renew a session already expired by the ZK server.
> From ZK server log, session 25cd1e82c110001 was expired at 22:04:39.
> {code:java}
> June 27th 2017, 22:04:39.000 INFO
> org.apache.zookeeper.server.ZooKeeperServer Expiring session
> 0x25cd1e82c110001, timeout of 12000ms exceeded
> June 27th 2017, 22:04:39.001 DEBUG
> org.apache.zookeeper.server.quorum.Leader Proposing::
> sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
> txntype:-11 reqpath:n/a
> June 27th 2017, 22:04:39.001 INFO
> org.apache.zookeeper.server.PrepRequestProcessorProcessed session
> termination for sessionid: 0x25cd1e82c110001
> June 27th 2017, 22:04:39.001 DEBUG
> org.apache.zookeeper.server.quorum.CommitProcessor Processing request::
> sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
> txntype:-11 reqpath:n/a
> June 27th 2017, 22:05:20.324 INFO
> org.apache.zookeeper.server.quorum.Learner Revalidating client:
> 0x25cd1e82c110001
> June 27th 2017, 22:05:20.324 INFO
> org.apache.zookeeper.server.ZooKeeperServer Client attempting to renew
> session 0x25cd1e82c110001 at /100.96.5.6:47618
> June 27th 2017, 22:05:20.325 INFO
> org.apache.zookeeper.server.ZooKeeperServer Established session
> 0x25cd1e82c110001 with negotiated timeout 12000 for client /100.96.5.6:47618
> {code}
> From ZK client's log, it was able to renew the expired session on 22:05:20.
> {code:java}
> June 27th 2017, 22:05:18.590 INFOorg.apache.zookeeper.ClientCnxn Client
> session timed out, have not heard from server in 4485ms for sessionid
> 0x25cd1e82c110001, closing socket connection and attempting reconnect 0
> June 27th 2017, 22:05:18.590 WARNorg.apache.zookeeper.ClientCnxn Client
> session timed out, have not heard from server in 4485ms for sessionid
> 0x25cd1e82c110001 0
> June 27th 2017, 22:05:19.325 WARNorg.apache.zookeeper.ClientCnxn SASL
> configuration failed: javax.security.auth.login.LoginException: No JAAS
> configuration section named 'Client' was found in specified JAAS
> configuration file: '/opt/confluent/etc/kafka/server_jaas.conf'. Will
> continue connection to Zookeeper server without SASL authentication, if
> Zookeeper server allows it. 0
> June 27th 2017, 22:05:19.326 INFOorg.apache.zookeeper.ClientCnxn Opening
> socket connection to server 100.65.188.168/100.65.188.168:2181 0
> June 27th 2017, 22:05:20.324 INFOorg.apache.zookeeper.ClientCnxn Socket
> connection established to 100.65.188.168/100.65.188.168:2181, initiating
> session 0
> June 27th 2017, 22:05:20.327 INFOorg.apache.zookeeper.ClientCnxn Session
> establishment complete on server 100.65.188.168/100.65.188.168:2181,
> sessionid = 0x25cd1e82c110001, negotiated timeout = 12000 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ZOOKEEPER-2867) an expired ZK session can be re-established
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated ZOOKEEPER-2867:
---
Attachment: zk.1.formatted
zk.0.formatted
[~hanm], thanks for the reply. I am attaching the log of 2 of the 3 ZK servers
around that time. During that window, there was some potential network issue
that may prevent ZK servers from talking to each other. The network issue seems
to be gone after 22:05:20, when the ZK cluster stabilized again.
Assuming that session 25cd1e82c110001 didn't really get expired at that point,
I got a followup question. A month later, the whole ZK cluster was done and was
restarted. On restarting, I saw the following logging in ZK server about
deleting an ephemeral in that session.
August 2nd 2017, 23:41:55.076 DEBUG org.apache.zookeeper.server.DataTree
Deleting ephemeral node /cp15/brokers/ids/0 for session 0x25cd1e82c110001
I assume that's because ZK server thinks that session is expired? However, in
ZK server's commit log, I didn't find any entry about closing that session. Is
that normal? Thanks,
> an expired ZK session can be re-established
> ---
>
> Key: ZOOKEEPER-2867
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2867
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.10
>Reporter: Jun Rao
> Attachments: zk.0.formatted, zk.1.formatted
>
>
> Not sure if this is a real bug, but I found an instance when a ZK client
> seems to be able to renew a session already expired by the ZK server.
> From ZK server log, session 25cd1e82c110001 was expired at 22:04:39.
> {code:java}
> June 27th 2017, 22:04:39.000 INFO
> org.apache.zookeeper.server.ZooKeeperServer Expiring session
> 0x25cd1e82c110001, timeout of 12000ms exceeded
> June 27th 2017, 22:04:39.001 DEBUG
> org.apache.zookeeper.server.quorum.Leader Proposing::
> sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
> txntype:-11 reqpath:n/a
> June 27th 2017, 22:04:39.001 INFO
> org.apache.zookeeper.server.PrepRequestProcessorProcessed session
> termination for sessionid: 0x25cd1e82c110001
> June 27th 2017, 22:04:39.001 DEBUG
> org.apache.zookeeper.server.quorum.CommitProcessor Processing request::
> sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
> txntype:-11 reqpath:n/a
> June 27th 2017, 22:05:20.324 INFO
> org.apache.zookeeper.server.quorum.Learner Revalidating client:
> 0x25cd1e82c110001
> June 27th 2017, 22:05:20.324 INFO
> org.apache.zookeeper.server.ZooKeeperServer Client attempting to renew
> session 0x25cd1e82c110001 at /100.96.5.6:47618
> June 27th 2017, 22:05:20.325 INFO
> org.apache.zookeeper.server.ZooKeeperServer Established session
> 0x25cd1e82c110001 with negotiated timeout 12000 for client /100.96.5.6:47618
> {code}
> From ZK client's log, it was able to renew the expired session on 22:05:20.
> {code:java}
> June 27th 2017, 22:05:18.590 INFOorg.apache.zookeeper.ClientCnxn Client
> session timed out, have not heard from server in 4485ms for sessionid
> 0x25cd1e82c110001, closing socket connection and attempting reconnect 0
> June 27th 2017, 22:05:18.590 WARNorg.apache.zookeeper.ClientCnxn Client
> session timed out, have not heard from server in 4485ms for sessionid
> 0x25cd1e82c110001 0
> June 27th 2017, 22:05:19.325 WARNorg.apache.zookeeper.ClientCnxn SASL
> configuration failed: javax.security.auth.login.LoginException: No JAAS
> configuration section named 'Client' was found in specified JAAS
> configuration file: '/opt/confluent/etc/kafka/server_jaas.conf'. Will
> continue connection to Zookeeper server without SASL authentication, if
> Zookeeper server allows it. 0
> June 27th 2017, 22:05:19.326 INFOorg.apache.zookeeper.ClientCnxn Opening
> socket connection to server 100.65.188.168/100.65.188.168:2181 0
> June 27th 2017, 22:05:20.324 INFOorg.apache.zookeeper.ClientCnxn Socket
> connection established to 100.65.188.168/100.65.188.168:2181, initiating
> session 0
> June 27th 2017, 22:05:20.327 INFOorg.apache.zookeeper.ClientCnxn Session
> establishment complete on server 100.65.188.168/100.65.188.168:2181,
> sessionid = 0x25cd1e82c110001, negotiated timeout = 12000 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ZOOKEEPER-2867) an expired ZK session can be re-established
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated ZOOKEEPER-2867:
---
Description:
Not sure if this is a real bug, but I found an instance when a ZK client seems
to be able to renew a session already expired by the ZK server.
>From ZK server log, session 25cd1e82c110001 was expired at 22:04:39.
{code:java}
June 27th 2017, 22:04:39.000INFO
org.apache.zookeeper.server.ZooKeeperServer Expiring session
0x25cd1e82c110001, timeout of 12000ms exceeded
June 27th 2017, 22:04:39.001DEBUG
org.apache.zookeeper.server.quorum.Leader Proposing::
sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
txntype:-11 reqpath:n/a
June 27th 2017, 22:04:39.001INFO
org.apache.zookeeper.server.PrepRequestProcessorProcessed session
termination for sessionid: 0x25cd1e82c110001
June 27th 2017, 22:04:39.001DEBUG
org.apache.zookeeper.server.quorum.CommitProcessor Processing request::
sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
txntype:-11 reqpath:n/a
June 27th 2017, 22:05:20.324INFO
org.apache.zookeeper.server.quorum.Learner Revalidating client:
0x25cd1e82c110001
June 27th 2017, 22:05:20.324INFO
org.apache.zookeeper.server.ZooKeeperServer Client attempting to renew
session 0x25cd1e82c110001 at /100.96.5.6:47618
June 27th 2017, 22:05:20.325INFO
org.apache.zookeeper.server.ZooKeeperServer Established session
0x25cd1e82c110001 with negotiated timeout 12000 for client /100.96.5.6:47618
{code}
>From ZK client's log, it was able to renew the expired session on 22:05:20.
{code:java}
June 27th 2017, 22:05:18.590INFOorg.apache.zookeeper.ClientCnxn Client
session timed out, have not heard from server in 4485ms for sessionid
0x25cd1e82c110001, closing socket connection and attempting reconnect 0
June 27th 2017, 22:05:18.590WARNorg.apache.zookeeper.ClientCnxn Client
session timed out, have not heard from server in 4485ms for sessionid
0x25cd1e82c110001 0
June 27th 2017, 22:05:19.325WARNorg.apache.zookeeper.ClientCnxn SASL
configuration failed: javax.security.auth.login.LoginException: No JAAS
configuration section named 'Client' was found in specified JAAS configuration
file: '/opt/confluent/etc/kafka/server_jaas.conf'. Will continue connection to
Zookeeper server without SASL authentication, if Zookeeper server allows it. 0
June 27th 2017, 22:05:19.326INFOorg.apache.zookeeper.ClientCnxn Opening
socket connection to server 100.65.188.168/100.65.188.168:2181 0
June 27th 2017, 22:05:20.324INFOorg.apache.zookeeper.ClientCnxn Socket
connection established to 100.65.188.168/100.65.188.168:2181, initiating
session 0
June 27th 2017, 22:05:20.327INFOorg.apache.zookeeper.ClientCnxn Session
establishment complete on server 100.65.188.168/100.65.188.168:2181, sessionid
= 0x25cd1e82c110001, negotiated timeout = 12000 0
{code}
was:
Not sure if this is a real bug, but I found an instance when a ZK client seems
to be able to renew a session already expired by the ZK server.
>From ZK server log, session 25cd1e82c110001 was expired at 22:04:39.
{code:java}
June 27th 2017, 22:04:39.0001 INFO
org.apache.zookeeper.server.ZooKeeperServer Expiring session
0x25cd1e82c110001, timeout of 12000ms exceeded
June 27th 2017, 22:04:39.0011 DEBUG
org.apache.zookeeper.server.quorum.Leader Proposing::
sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
txntype:-11 reqpath:n/a
June 27th 2017, 22:04:39.0011 INFO
org.apache.zookeeper.server.PrepRequestProcessorProcessed session
termination for sessionid: 0x25cd1e82c110001
June 27th 2017, 22:04:39.0011 DEBUG
org.apache.zookeeper.server.quorum.CommitProcessor Processing request::
sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
txntype:-11 reqpath:n/a
June 27th 2017, 22:05:20.3232 DEBUG
org.apache.zookeeper.server.quorum.Leader Proposing::
sessionid:0x25cd1e82c110001 type:setData cxid:0xdc zxid:0x3047b txntype:5
reqpath:n/a
June 27th 2017, 22:05:20.3232 DEBUG
org.apache.zookeeper.server.quorum.CommitProcessor Processing request::
sessionid:0x25cd1e82c110001 type:setData cxid:0xdc zxid:0x3047b txntype:5
reqpath:n/a
June 27th 2017, 22:05:20.3241 INFO
org.apache.zookeeper.server.quorum.Learner Revalidating client:
0x25cd1e82c110001
June 27th 2017, 22:05:20.3241 INFO
org.apache.zookeeper.server.ZooKeeperServer Client attempting to renew
session 0x25cd1e82c110001 at /100.96.5.6:47618
June 27th 2017, 22:05:20.3251 INFO
org.apache.zookeeper.server.ZooKeeperServer Established session
0x25cd1e82c110001 with negotiated timeout 12000 for client /100.96.5.6:47618
{code}
