You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Sumit Arrawatia (JIRA)" <ji...@apache.org> on 2016/07/29 21:02:20 UTC

[jira] [Updated] (KAFKA-4006) Kafka connect fails sometime with InvalidTopicException in distributed mode

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

Sumit Arrawatia updated KAFKA-4006:
-----------------------------------
    Description: 
I get trying to spin up a 3 node distributed connect cluster.

Sometimes one of the worker fails to boot with the following error when auto topic creation is enabled : 

org.apache.kafka.common.errors.InvalidTopicException: Topic 'default.config' is invalid 

default.config is the topic name for Connect config. 

Also, starting the worker again fixes the issue. 



  was:
I get trying to spin up a 3 node distributed connect cluster.

Sometimes one of the worker fails to boot with the following error when auto topic creation is enabled : `org.apache.kafka.common.errors.InvalidTopicException: Topic 'default.config' is invalid` error . 

`default.config` is the topic name for Connect config. 

Also, starting the worker again fixes the issue. 




> Kafka connect fails sometime with InvalidTopicException in distributed mode
> ---------------------------------------------------------------------------
>
>                 Key: KAFKA-4006
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4006
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 0.10.0.0
>            Reporter: Sumit Arrawatia
>            Assignee: Ewen Cheslack-Postava
>
> I get trying to spin up a 3 node distributed connect cluster.
> Sometimes one of the worker fails to boot with the following error when auto topic creation is enabled : 
> org.apache.kafka.common.errors.InvalidTopicException: Topic 'default.config' is invalid 
> default.config is the topic name for Connect config. 
> Also, starting the worker again fixes the issue. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)