You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Graham Campbell (Jira)" <ji...@apache.org> on 2020/01/02 18:45:00 UTC
[jira] [Commented] (KAFKA-8508) saslClient failed to initialize
properly: it's null.
[ https://issues.apache.org/jira/browse/KAFKA-8508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007003#comment-17007003 ]
Graham Campbell commented on KAFKA-8508:
----------------------------------------
This specific ArrayIndexOutOfBoundsException is actually due to ZOOKEEPER-2323, which is fixed in ZK 3.5.2
> saslClient failed to initialize properly: it's null.
> ----------------------------------------------------
>
> Key: KAFKA-8508
> URL: https://issues.apache.org/jira/browse/KAFKA-8508
> Project: Kafka
> Issue Type: Bug
> Components: zkclient
> Affects Versions: 2.0.1
> Reporter: Caroline Liu
> Priority: Major
>
> After a network issue caused the last ISR to fail connecting to ZooKeeper, the attempt to reconnect failed with an ArrayIndexOutOfBoundsException.
> {code:java}
> 2019-05-31 15:54:38,823 [zk-session-expiry-handler0-SendThread(zk2-1:2181)] WARN (org.apache.zookeeper.ClientCnxn) - Client session timed out, have not heard from server in 20010ms for sessionid 0x15000011b2b1042a
> 2019-05-31 15:54:38,823 [zk-session-expiry-handler0-SendThread(zk2-1:2181)] INFO (org.apache.zookeeper.ClientCnxn) - Client session timed out, have not heard from server in 20010ms for sessionid 0x15000011b2b1042a, closing socket connection and attempting reconnect
> 2019-05-31 15:54:39,702 [zk-session-expiry-handler0-SendThread(zk1-2:2181)] INFO (org.apache.zookeeper.client.ZooKeeperSaslClient) - Client will use DIGEST-MD5 as SASL mechanism.
> 2019-05-31 15:54:39,702 [zk-session-expiry-handler0-SendThread(zk1-2:2181)] ERROR (org.apache.zookeeper.client.ZooKeeperSaslClient) - Exception while trying to create SASL client: java.lang.ArrayIndexOutOfBoundsException: 0
> 2019-05-31 15:54:39,702 [zk-session-expiry-handler0-SendThread(zk1-2:2181)] INFO (org.apache.zookeeper.ClientCnxn) - Opening socket connection to server zk1-2/1.3.6.1:2181. Will attempt to SASL-authenticate using Login Context section 'Client'
> 2019-05-31 15:54:39,702 [zk-session-expiry-handler0-SendThread(zk1-2:2181)] INFO (org.apache.zookeeper.ClientCnxn) - Socket connection established to zk1-2/1.3.6.1:2181, initiating session
> 2019-05-31 15:54:39,703 [zk-session-expiry-handler0-SendThread(zk1-2:2181)] INFO (org.apache.zookeeper.ClientCnxn) - Session establishment complete on server zk1-2/1.3.6.1:2181, sessionid = 0x15000011b2b1042a, negotiated timeout = 30000
> 2019-05-31 15:54:39,703 [zk-session-expiry-handler0-SendThread(zk1-2:2181)] ERROR (org.apache.zookeeper.ClientCnxn) - SASL authentication with Zookeeper Quorum member failed: javax.security.sasl.SaslException: saslClient failed to initialize properly: it's null.{code}
> Kafka was "not live" in zookeeper and had to be manually restarted to recover from this error. It would be better if the last ISR could retry.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)