arshadmohammad opened a new issue, #3101:
URL: https://github.com/apache/helix/issues/3101

   ### Describe the bug
   When enabling Kerberos authentication for Zookeeper, the Helix Controller 
fails to start due to a timeout in the Zookeeper client connection. The client 
transitions to the SaslAuthenticated state instead of SyncConnected, causing 
the waitForEstablishedSession method to timeout.
   
   ### Observed Behavior:
   2026/02/19 10:37:12.994 ERROR [HelixControllerMain] [main] Exception while 
starting controller
   org.apache.helix.zookeeper.zkclient.exception.ZkTimeoutException: Waiting to 
be connected to ZK server has timed out.
           at 
org.apache.helix.zookeeper.zkclient.ZkClient.waitForEstablishedSession(ZkClient.java:1990)
           at 
org.apache.helix.manager.zk.ZKHelixManager.createClient(ZKHelixManager.java:775)
           at 
org.apache.helix.manager.zk.ZKHelixManager.connect(ZKHelixManager.java:817)
           at 
org.apache.helix.controller.HelixControllerMain.startHelixController(HelixControllerMain.java:159)
           at 
org.apache.pinot.controller.helix.core.util.HelixSetupUtils.setupHelixController(HelixSetupUtils.java:131)
   ### To Reproduce
   1.Enable Kerberos authentication for Zookeeper.
   2. Start the Helix Controller.
   
   ### Expected behavior
   The controller should recognize SaslAuthenticated as a valid connected state 
and proceed with startup.
   
   ### Additional context
   See: https://github.com/apache/pinot/issues/17729 for more details.
   
   Environment:
   Apache Pinot Controller:  version 1.4.0
   Helix. 1.3.2
   Zookeeper with Kerberos authentication enabled: 3.9.3
   
   ### Root Cause:
   The waitForEstablishedSession method only recognizes SyncConnected as a 
valid state, ignoring SaslAuthenticated, which leads to a timeout.


-- 
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]

Reply via email to