Shikhar Bhushan commented on KAFKA-4306:

KAFKA-4154 is another issue relating to broker-unavailability preventing 
shutdown, but I believe there it's because it failed to finish startup in the 
first place.

> 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:
>            Reporter: Gwen Shapira
>            Assignee: Ewen Cheslack-Postava
> 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 (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

Reply via email to