You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Yuqi Gu (JIRA)" <ji...@apache.org> on 2019/07/08 09:20:00 UTC
[jira] [Commented] (BIGTOP-3208) Exception in master branch (and
branch-1.4): kafka-server failed to launch due to missing zookeeper
AsyncCallback.MultiCallback
[ https://issues.apache.org/jira/browse/BIGTOP-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880146#comment-16880146 ]
Yuqi Gu commented on BIGTOP-3208:
---------------------------------
Kafka-2.1.1 requires zookeeper 3.4.7+.
How about to revert Kafka to 0.10.2.2 in master branch? [~evans_ye]
> Exception in master branch (and branch-1.4): kafka-server failed to launch due to missing zookeeper AsyncCallback.MultiCallback
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: BIGTOP-3208
> URL: https://issues.apache.org/jira/browse/BIGTOP-3208
> Project: Bigtop
> Issue Type: Bug
> Components: general
> Affects Versions: 1.4.0
> Reporter: Guodong Xu
> Priority: Major
>
> Short: Upgrading Kafka to 2.1.1 requires Zookeeper v3.4.7 or later. However, what we have now is only zookeeper 3.4.6.
>
> I am working on branch 'master' (commit id: 0259005). When I set up a multi-node container-based cluster (./provisioner/docker/docker-hadoop.sh -C xxx.yaml -c 3), I noticed this error, which is fatal to Kafka-server: "java.lang.NoClassDefFoundError:org/apache/zookeeper/AsyncCallback$MultiCallback
> "
> Logs are in below. A further look into /var/log/kafka/kafka-server.out shows that root cause of this problem is 'AsyncCallback MultiCallback' is defined in Zookeeper only since 3.4.7. However, Bigtop master (and branch-1.4) includes Zookeeper 3.4.6.
>
> See here for similar discussion from Spark community: [https://mail-archives.apache.org/mod_mbox/spark-reviews/201811.mbox/%3Cgit-pr-23119-spark@git.apache.org%3E]
>
> Kafka version is upgraded to 2.1.1 in Bigtop master and branch-1.4.
>
> In Bigtop 1.3, Kafka version is 0.10.2.2, and it runs well with Zookeeper 3.4.6. That's why I didn't such error in previous releases like Bigtop 1.3.
>
> ==
> master branch or 1.4.0:
> Error: Could not start Service[kafka-server]: Execution of '/usr/bin/systemctl start kafka-server' returned 1: Job for kafka-server.service failed because the control process exited with error code. See "systemctl status kafka-server.service" and "journalctl -xe" for details.
> Wrapped exception:
> Execution of '/usr/bin/systemctl start kafka-server' returned 1: Job for kafka-server.service failed because the control process exited with error code. See "systemctl status kafka-server.service" and "journalctl -xe" for details.
> Error: /Stage[main]/Kafka::Server/Service[kafka-server]/ensure: change from stopped to running failed: Could not start Service[kafka-server]: Execution of '/usr/bin/systemctl start kafka-server' returned 1: Job for kafka-server.service failed because the control process exited with error code. See "systemctl status kafka-server.service" and "journalctl -xe" for details.
>
> [root@63f5c5a99d8d /]# systemctl status kafka-server.service
> ● kafka-server.service - LSB: Kafka Server
> Loaded: loaded (/etc/rc.d/init.d/kafka-server; bad; vendor preset: disabled)
> Active: failed (Result: exit-code) since Mon 2019-04-15 03:48:45 UTC; 1min 29s ago
> Docs: man:systemd-sysv-generator(8)
>
> Apr 15 03:48:42 63f5c5a99d8d systemd[1]: Starting LSB: Kafka Server...
> Apr 15 03:48:42 63f5c5a99d8d kafka-server[9344]: Starting Kafka Server (kafka-server):[ OK ]
> Apr 15 03:48:42 63f5c5a99d8d kafka-server[9344]: Starting (kafka-server):
> Apr 15 03:48:42 63f5c5a99d8d su[9370]: (to kafka) root on none
> Apr 15 03:48:45 63f5c5a99d8d kafka-server[9344]: Failure to start Kafka Server (kafka-server). Return value: 1[FAILED]
> Apr 15 03:48:45 63f5c5a99d8d systemd[1]: kafka-server.service: control process exited, code=exited status=1
> Apr 15 03:48:45 63f5c5a99d8d systemd[1]: Failed to start LSB: Kafka Server.
> Apr 15 03:48:45 63f5c5a99d8d systemd[1]: Unit kafka-server.service entered failed state.
> Apr 15 03:48:45 63f5c5a99d8d systemd[1]: kafka-server.service failed.
>
> = /var/log/kafka/kafka-server.out
> java.lang.NoClassDefFoundError: org/apache/zookeeper/AsyncCallback$MultiCallback
> at kafka.zk.KafkaZkClient$.apply(KafkaZkClient.scala:1693)
> at kafka.server.KafkaServer.kafka$server$KafkaServer$$createZkClient$1(KafkaServer.scala:348)
> at kafka.server.KafkaServer.initZkClient(KafkaServer.scala:372)
> at kafka.server.KafkaServer.startup(KafkaServer.scala:202)
> at kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:38)
> at kafka.Kafka$.main(Kafka.scala:75)
> at kafka.Kafka.main(Kafka.scala)
>
> Caused by: java.lang.ClassNotFoundException: org.apache.zookeeper.AsyncCallback$MultiCallback
> at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 7 more
> [2019-04-15 03:55:24,859] INFO shutting down (kafka.server.KafkaServer)
> [2019-04-15 03:55:24,865] INFO shut down completed (kafka.server.KafkaServer)
> [2019-04-15 03:55:24,865] ERROR Exiting Kafka. (kafka.server.KafkaServerStartable)
> [2019-04-15 03:55:24,868] INFO shutting down (kafka.server.KafkaServer)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)