LZD-PratyushBhatt opened a new issue, #3036: URL: https://github.com/apache/helix/issues/3036
### Describe the bug The issue is related to ZooKeeper's TTL (Time-To-Live) node functionality and specifically how it behaves in the embedded ZooKeeper environment used in tests. In a normal ZooKeeper deployment, a background ContainerManager thread runs periodically to clean up expired TTL nodes. However, in the embedded ZooKeeper used for testing, this background thread doesn't appear to be functioning properly. The ContainerManager is designed to run on a configurable schedule (default is 60 seconds), but in the test environment, this cleanup process doesn't happen. ### To Reproduce Trigger `[testSyncCreateWithTTL()](https://github.com/apache/helix/blob/5de9232d98f0aa4391eebfce51ca61ef72cc1c2e/helix-core/src/test/java/org/apache/helix/manager/zk/TestZkBaseDataAccessor.java#L246)` in debug mode while setting up a breakpoint [here](https://github.com/apache/helix/blob/5de9232d98f0aa4391eebfce51ca61ef72cc1c2e/helix-core/src/test/java/org/apache/helix/manager/zk/TestZkBaseDataAccessor.java#L272), then analyse the znode in zk. It will never be cleaned up. ### Expected behavior The znodes should get cleaned up in the integration tests once the TTL expires ### Additional context The tests that target PERSISTENT_WITH_TTL are incomplete. They dont check if the znode is removed or they just remove the znode manually. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
