Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Elastic5 connector fails to start up

See original GitHub issue

Hello! I have a problem deploying the elastic 5 connector to Kubernetes. It looks like the Kafka Connect service fails to start up. Here are the last lines of the pod log:

===> Launching kafka-connect ...
Waiting for connect's rest API at http://10.244.3.161:9102
2017-09-06 14:22:44.075:INFO:ipjsoejs.Server:jetty-8.y.z-SNAPSHOT
2017-09-06 14:22:44.176:INFO:ipjsoejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:9102
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/etc/datamountaineer/jars/kafka-connect-elastic5-0.3.0-3.3.0-all.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/share/java/kafka/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/share/java/kafka-connect-hdfs/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
Waiting for connect's rest API at http://10.244.3.161:9102
Waiting for connect's rest API at http://10.244.3.161:9102
Waiting for connect's rest API at http://10.244.3.161:9102
Waiting for connect's rest API at http://10.244.3.161:9102
Waiting for connect's rest API at http://10.244.3.161:9102
Waiting for connect's rest API at http://10.244.3.161:9102
Waiting for connect's rest API at http://10.244.3.161:9102
Waiting for connect's rest API at http://10.244.3.161:9102
Waiting for connect's rest API at http://10.244.3.161:9102
Waiting for connect's rest API at http://10.244.3.161:9102
Waiting for connect's rest API at http://10.244.3.161:9102
Exception in thread "main" java.lang.NoSuchMethodError: com.google.common.collect.Sets$SetView.iterator()Lcom/google/common/collect/UnmodifiableIterator;
	at org.reflections.Reflections.expandSuperTypes(Reflections.java:380)
	at org.reflections.Reflections.<init>(Reflections.java:126)
	at org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader.scanPluginPath(DelegatingClassLoader.java:221)
	at org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader.scanUrlsAndAddPlugins(DelegatingClassLoader.java:198)
	at org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader.initLoaders(DelegatingClassLoader.java:159)
	at org.apache.kafka.connect.runtime.isolation.Plugins.<init>(Plugins.java:47)
	at org.apache.kafka.connect.cli.ConnectDistributed.main(ConnectDistributed.java:63)

I would appreciate any help in investigating the problem 😃 If it helps, I can show the full pod log.

Issue Analytics

State:
Created 6 years ago
Comments:14

Top GitHub Comments

3reactions

andrewstevensoncommented, Sep 6, 2017

can you check the contents of /etc/kafka-connect/kafka-connect.properties. it should have plugin.path which points to /etc/datamountaineer/jars this gives classloader isolation.

1reaction

andrewstevensoncommented, Sep 6, 2017

It’s building and pushing now.

Top Results From Across the Web

Elastic 5 Sink - Lenses Documentation

The Sink will automatically create missing indexes at startup. Error Polices¶. Landoop sink connectors support error polices. These error polices allow you ...

mongo-connector is not working with elasticsearch 2 #813

elastic2-doc-manager and mongo-connector has been installed. ... or: pip install elastic-doc-manager[elastic5] ... This is the startup script: `#!/bin/bash.

unable to run mongo-connector - Stack Overflow

Here's how to do this: Generate a mongo-connector timestamp file: Run mongo-connector --no-dump. Stop mongo-connector right after it starts up.

Connector could not be started for the following reason: failed ...

Common causes. Below are some common causes of JVM startup problems: Assigning too large of a maximum heap size to the JVM.

Troubleshooting and limitations | Kibana Guide [8.5] - Elastic

Alerting provides many options for diagnosing problems with rules and connectors. Check the Kibana logedit. Rules and connectors log to the Kibana logger ......