Affects Version/s: 3.4.13
Fix Version/s: None
App AA connects to ZooKeeper and creates a temporary path such as /brokers/ids/10. Another APP BB also connects to ZooKeeper. At some point AA BB and ZooKeeper are restarted, and BB allocates AA's old session
AA connect to zookeeper ,and log in zk:
[2021-03-07 08:47:43,468] INFO [SyncThread:0] Established session 0x10000053ef90000 with negotiated timeout 8000 for client /126.96.36.199:59966 (org.apache.zookeeper.server.ZooKeeperServer)
BB connect to zookeeper ,and log in zk:
[2021-03-07 08:58:51,351] INFO [SyncThread:0] Established session 0x10000053ef90000 with negotiated timeout 30000 for client /188.8.131.52:39360 (org.apache.zookeeper.server.ZooKeeperServer)
I understand that after a restart, ZooKeeper loads old transaction logs and snapshot files, and old sessions and temporary paths are loaded. If BB obtains the old session 0x10000053ef90000 at this point, the session will not expire and the temporary path will not be deleted, causing AA to be unable to re-register the temporary path
This is my question. I look forward to your help. Thank you very much!
I have checked the source code of zookeeper, and the generation of session is as follows:
Id is a fixed value, and the only variable that affects session id is the current time. Obviously zookeeper it takes different time to create session twice, but why get the same session id?