You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/01 23:35:59 UTC
[jira] [Commented] (KAFKA-4306) Connect workers won't shut down if
brokers are not available
[ https://issues.apache.org/jira/browse/KAFKA-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713416#comment-15713416 ]
ASF GitHub Bot commented on KAFKA-4306:
---------------------------------------
GitHub user kkonstantine opened a pull request:
https://github.com/apache/kafka/pull/2201
KAFKA-4306: Shutdown distributed herder with a timeout.
Resolves
KAFKA-4306: Connect workers won't shut down if brokers are not available
KAFKA-4154: Kafka Connect fails to shutdown if it has not completed startup
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kkonstantine/kafka KAFKA-4306-Connect-workers-will-not-shut-down-if-brokers-are-not-available
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2201.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2201
----
commit b1decf8ab09ae8e89288d7548cc7561e2455aa0d
Author: Konstantine Karantasis <ko...@confluent.io>
Date: 2016-11-12T00:55:07Z
KAFKA-4306: Shutdown distributed herder with a timeout.
Resolves
KAFKA-4306: Connect workers won't shut down if brokers are not available
KAFKA-4154: Kafka Connect fails to shutdown if it has not completed startup
----
> Connect workers won't shut down if brokers are not available
> ------------------------------------------------------------
>
> Key: KAFKA-4306
> URL: https://issues.apache.org/jira/browse/KAFKA-4306
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 0.10.1.0
> Reporter: Gwen Shapira
> Assignee: Konstantine Karantasis
>
> If brokers are not available and we try to shut down connect workers, sink connectors will be stuck in a loop retrying to commit offsets:
> 2016-10-17 09:39:14,907] INFO Marking the coordinator 192.168.1.9:9092 (id: 2147483647 rack: null) dead for group connect-dump-kafka-config1 (org.apache.kafka.clients.consumer.internals.AbstractCoordinator:600)
> [2016-10-17 09:39:14,907] ERROR Commit of WorkerSinkTask{id=dump-kafka-config1-0} offsets threw an unexpected exception: (org.apache.kafka.connect.runtime.WorkerSinkTask:194)
> org.apache.kafka.clients.consumer.RetriableCommitFailedException: Offset commit failed with a retriable exception. You should retry committing offsets.
> Caused by: org.apache.kafka.common.errors.GroupCoordinatorNotAvailableException
> We should probably limit the number of retries before doing "unclean" shutdown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)