[
https://issues.apache.org/jira/browse/KAFKA-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-3423.
------------------------------------------
Resolution: Duplicate
Reviewer: Ewen Cheslack-Postava
Thanks for the report, this looks like a dup of another bug we already have
filed.
> can't start kafka connect with former configs in distributed mode
> -----------------------------------------------------------------
>
> Key: KAFKA-3423
> URL: https://issues.apache.org/jira/browse/KAFKA-3423
> Project: Kafka
> Issue Type: Bug
> Components: copycat
> Affects Versions: 0.9.0.0, 0.9.0.1
> Environment: linux.
> 2 connect distributed nodes.
> Reporter: HaojingMa
> Assignee: Ewen Cheslack-Postava
> Priority: Critical
>
> firstly, i post one job's configuration. Then i shutdown one. And restart it
> later. But the connect cluster goes down.
> I go through the code, and find in method completeTaskIdSet of
> KafkaConfigStorage class. The argument idSet may be a null point.
> Cause you can't gurantee the sequence of configs when consumer consume the
> topic connect-config.
> Log like this
> [2016-03-17 15:59:06,209] ERROR Uncaught exception in herder work thread,
> exiting: (org.apache.kafka.connect.runtime.distributed.DistributedHerder:166)
> java.lang.NullPointerException
> at
> org.apache.kafka.connect.storage.KafkaConfigStorage.completeTaskIdSet(KafkaConfigStorage.java:558)
> at
> org.apache.kafka.connect.storage.KafkaConfigStorage.access$1200(KafkaConfigStorage.java:143)
> at
> org.apache.kafka.connect.storage.KafkaConfigStorage$1.onCompletion(KafkaConfigStorage.java:476)
> at
> org.apache.kafka.connect.storage.KafkaConfigStorage$1.onCompletion(KafkaConfigStorage.java:372)
> at
> org.apache.kafka.connect.util.KafkaBasedLog.poll(KafkaBasedLog.java:234)
> at
> org.apache.kafka.connect.util.KafkaBasedLog.readToLogEnd(KafkaBasedLog.java:274)
> at
> org.apache.kafka.connect.util.KafkaBasedLog.start(KafkaBasedLog.java:138)
> at
> org.apache.kafka.connect.storage.KafkaConfigStorage.start(KafkaConfigStorage.java:240)
> at
> org.apache.kafka.connect.runtime.distributed.DistributedHerder.run(DistributedHerder.java:154)
> at java.lang.Thread.run(Thread.java:745)
> [2016-03-17 15:59:07,233] INFO Kafka Connect stopping
> (org.apache.kafka.connect.runtime.Connect:68)
> [2016-03-17 15:59:07,242] INFO Stopped
> ServerConnector@2fbdc5dd{HTTP/1.1}{0.0.0.0:8083}
> (org.eclipse.jetty.server.ServerConnector:306)
> [2016-03-17 15:59:07,268] INFO Stopped
> o.e.j.s.ServletContextHandler@1d733944{/,null,UNAVAILABLE}
> (org.eclipse.jetty.server.handler.ContextHandler:865)
> [2016-03-17 15:59:07,272] INFO Herder stopping
> (org.apache.kafka.connect.runtime.distributed.DistributedHerder:310)
> [2016-03-17 15:59:07,272] INFO Herder stopped
> (org.apache.kafka.connect.runtime.distributed.DistributedHerder:331)
> [2016-03-17 15:59:07,273] INFO Worker stopping
> (org.apache.kafka.connect.runtime.Worker:115)
> [2016-03-17 15:59:07,273] INFO Stopping KafkaOffsetBackingStore
> (org.apache.kafka.connect.storage.KafkaOffsetBackingStore:91)
> [2016-03-17 15:59:07,273] INFO Stopping KafkaBasedLog for topic
> connect-offsets (org.apache.kafka.connect.util.KafkaBasedLog:149)
> [2016-03-17 15:59:07,274] INFO Closing the Kafka producer with timeoutMillis
> = 9223372036854775807 ms.
> (org.apache.kafka.clients.producer.KafkaProducer:615)
> [2016-03-17 15:59:07,284] INFO Stopped KafkaBasedLog for topic
> connect-offsets (org.apache.kafka.connect.util.KafkaBasedLog:175)
> [2016-03-17 15:59:07,284] INFO Stopped KafkaOffsetBackingStore
> (org.apache.kafka.connect.storage.KafkaOffsetBackingStore:93)
> [2016-03-17 15:59:07,284] INFO Worker stopped
> (org.apache.kafka.connect.runtime.Worker:155)
> [2016-03-17 15:59:07,284] INFO Kafka Connect stopped
> (org.apache.kafka.connect.runtime.Connect:74)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
