kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantine Karantasis (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (KAFKA-4306) Connect workers won't shut down if brokers are not available
Date Mon, 14 Nov 2016 19:54:59 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Konstantine Karantasis reassigned KAFKA-4306:
---------------------------------------------

    Assignee: Konstantine Karantasis  (was: Ewen Cheslack-Postava)

> 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)

Mime
View raw message