Arch Linux User Repository

@servitkar it looks like they're not included in the start-script of the official distribution either. Therefore I removed them from the service file as well...

with jdk-openjdk=15:

kafka[308588]: Unrecognized VM option 'CMSClassUnloadingEnabled'
kafka[329124]: Unrecognized VM option 'CMSScavengeBeforeRemark'

works, when omitted from systemd_kafka.service (or from installed /usr/lib/systemd/system/kafka.service )

@cramaker Fixed! Thank you. Just updated and restarted Kafka and it all works fine now :)

@dxeoane Yeah that would probably work too. I was looking for where the JARs are located but couldn't find them.

@keeyan I have the same problem. In my case, i solved it by creating two symbolic links in the folder /usr/share/java/kafka to the files /usr/share/java/zookeeper/zookeeper-3.5.5.jar and /usr/share/java/zookeeper/zookeeper -jute-3.5.5.jar

@keenyan Great info - that let me track down the issue. I just pushed out a new pkgrel: give Kafka an update and let me know if that fixes things. Thanks!

@cramaker yeah I use yay so everything got updated together. Zookeeper is at 3.5.5-1. That said there is no file /usr/share/java/kafka/zookeeper*.jar although zookeeper is running fine. I have tried uninstalling both and reinstalling them again but there is no difference

@keenyan Did you install the recent Zookeeper update as well? I had to make a change to the Zookeeper client library included with the Kafka package:

/usr/share/java/kafka/zookeeper-3.4.14.jar

That used to be a symbolic link over to /usr/share/java/zookeeper/zookeeper-3.5.5.jar but that is now incompatible.

Let me know a.) what you're /usr/share/java/kafka & /usr/share/java/zookeeper directories look like - I suspect the issue may stem from the change of that symbolic link.

I installed an update today and now the Kafka service fails. Here is the relevant part of my var/log/kafka/server.log

[2019-07-19 00:50:05,442] ERROR Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
java.lang.NoClassDefFoundError: org/apache/zookeeper/KeeperException
    at kafka.server.KafkaServer.createZkClient$1(KafkaServer.scala:363)
    at kafka.server.KafkaServer.initZkClient(KafkaServer.scala:387)
    at kafka.server.KafkaServer.startup(KafkaServer.scala:207)
    at kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:38)
    at kafka.Kafka$.main(Kafka.scala:84)
    at kafka.Kafka.main(Kafka.scala)
Caused by: java.lang.ClassNotFoundException: org.apache.zookeeper.KeeperException
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
    ... 6 more
[2019-07-19 00:50:05,444] INFO shutting down (kafka.server.KafkaServer)
[2019-07-19 00:50:05,449] INFO shut down completed (kafka.server.KafkaServer)
[2019-07-19 00:50:05,449] ERROR Exiting Kafka. (kafka.server.KafkaServerStartable)
[2019-07-19 00:50:05,452] INFO shutting down (kafka.server.KafkaServer)

The Zookeeper service is up and running fine. Although for some reason it was dead earlier and I had to re enable it though.

Everything was working well before the update today so I think it's the update that broke it.

@Gedweb Please only mark the package as out-of-date if there is a new version available.

The reason you're getting the unrecognized option error is because you're using a JDK release prior to version 11. I couldn't maintain backwards compatibility when I chose these options. If you update to JDK 11 (which is now the default jdk-openjdk package), these options should work fine.

@fatalcoder Unfortunately, that's one of the options that I had to update in order to make it compatible with JDK 11