GrantPSpencer opened a new issue, #3073: URL: https://github.com/apache/helix/issues/3073
### Describe the bug Atomic drop creates a transaction to atomically delete all znodes under instance and config path. If this transaction exceeds the jute max buffer, then the client will disconnect from ZK and reconnect under the same session, but the operation will never succeed. ### To Reproduce In our case, the node had thousands of current and customized states. ### Expected behavior Deletion should either be achieved non-atomically or a proper exception should be thrown ### Additional context Atomic delete was implemented as we were facing recurrent issue of instance znodes being partially deleted, which lead to cluster getting into a bad state. Node could only be removed through manual intervention in ZK https://github.com/apache/helix/pull/2994 -- 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]
