[jira] [Commented] (KAFKA-5736) Improve error message in Connect when all kafka brokers are down
[ https://issues.apache.org/jira/browse/KAFKA-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770533#comment-16770533 ] Matthias J. Sax commented on KAFKA-5736: Moving all major/minor/trivial tickets that are not merged yet out of 2.2 release. > Improve error message in Connect when all kafka brokers are down > > > Key: KAFKA-5736 > URL: https://issues.apache.org/jira/browse/KAFKA-5736 > Project: Kafka > Issue Type: Bug > Components: KafkaConnect >Affects Versions: 0.11.0.0 >Reporter: Konstantine Karantasis >Assignee: Konstantine Karantasis >Priority: Major > Fix For: 2.2.0 > > Original Estimate: 3h > Remaining Estimate: 3h > > Currently when all the Kafka brokers are down, Kafka Connect is failing with > a pretty unintuitive message when it tries to, for instance, reconfigure > tasks. > Example output: > {code:java} > [2017-08-15 19:12:09,959] ERROR Failed to reconfigure connector's tasks, > retrying after backoff: > (org.apache.kafka.connect.runtime.distributed.DistributedHerder) > java.lang.IllegalArgumentException: CircularIterator can only be used on > non-empty lists > at > org.apache.kafka.common.utils.CircularIterator.(CircularIterator.java:29) > at > org.apache.kafka.clients.consumer.RoundRobinAssignor.assign(RoundRobinAssignor.java:61) > at > org.apache.kafka.clients.consumer.internals.AbstractPartitionAssignor.assign(AbstractPartitionAssignor.java:68) > at > ... (connector code) > at > org.apache.kafka.connect.runtime.Worker.connectorTaskConfigs(Worker.java:230) > {code} > The error message needs to be improved, since its root cause is the absence > kafka brokers for assignment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KAFKA-5736) Improve error message in Connect when all kafka brokers are down
[ https://issues.apache.org/jira/browse/KAFKA-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635637#comment-16635637 ] Dong Lin commented on KAFKA-5736: - Moving this to 2.2.0 since PR is not ready yet. > Improve error message in Connect when all kafka brokers are down > > > Key: KAFKA-5736 > URL: https://issues.apache.org/jira/browse/KAFKA-5736 > Project: Kafka > Issue Type: Bug > Components: KafkaConnect >Affects Versions: 0.11.0.0 >Reporter: Konstantine Karantasis >Assignee: Konstantine Karantasis >Priority: Major > Fix For: 2.1.0 > > Original Estimate: 3h > Remaining Estimate: 3h > > Currently when all the Kafka brokers are down, Kafka Connect is failing with > a pretty unintuitive message when it tries to, for instance, reconfigure > tasks. > Example output: > {code:java} > [2017-08-15 19:12:09,959] ERROR Failed to reconfigure connector's tasks, > retrying after backoff: > (org.apache.kafka.connect.runtime.distributed.DistributedHerder) > java.lang.IllegalArgumentException: CircularIterator can only be used on > non-empty lists > at > org.apache.kafka.common.utils.CircularIterator.(CircularIterator.java:29) > at > org.apache.kafka.clients.consumer.RoundRobinAssignor.assign(RoundRobinAssignor.java:61) > at > org.apache.kafka.clients.consumer.internals.AbstractPartitionAssignor.assign(AbstractPartitionAssignor.java:68) > at > ... (connector code) > at > org.apache.kafka.connect.runtime.Worker.connectorTaskConfigs(Worker.java:230) > {code} > The error message needs to be improved, since its root cause is the absence > kafka brokers for assignment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KAFKA-5736) Improve error message in Connect when all kafka brokers are down
[ https://issues.apache.org/jira/browse/KAFKA-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130930#comment-16130930 ] Konstantine Karantasis commented on KAFKA-5736: --- Not really and there's a good chance that it will be addressed in the specific Connector's context (the lines missing in the log above). I thought that when 1.0.0 was added as a target, 0.11.0.1 was removed. Removing now. Thanks [~damianguy]. > Improve error message in Connect when all kafka brokers are down > > > Key: KAFKA-5736 > URL: https://issues.apache.org/jira/browse/KAFKA-5736 > Project: Kafka > Issue Type: Bug > Components: KafkaConnect >Affects Versions: 0.11.0.0 >Reporter: Konstantine Karantasis >Assignee: Konstantine Karantasis > Fix For: 1.0.0 > > Original Estimate: 3h > Remaining Estimate: 3h > > Currently when all the Kafka brokers are down, Kafka Connect is failing with > a pretty unintuitive message when it tries to, for instance, reconfigure > tasks. > Example output: > {code:java} > [2017-08-15 19:12:09,959] ERROR Failed to reconfigure connector's tasks, > retrying after backoff: > (org.apache.kafka.connect.runtime.distributed.DistributedHerder) > java.lang.IllegalArgumentException: CircularIterator can only be used on > non-empty lists > at > org.apache.kafka.common.utils.CircularIterator.(CircularIterator.java:29) > at > org.apache.kafka.clients.consumer.RoundRobinAssignor.assign(RoundRobinAssignor.java:61) > at > org.apache.kafka.clients.consumer.internals.AbstractPartitionAssignor.assign(AbstractPartitionAssignor.java:68) > at > ... (connector code) > at > org.apache.kafka.connect.runtime.Worker.connectorTaskConfigs(Worker.java:230) > {code} > The error message needs to be improved, since its root cause is the absence > kafka brokers for assignment. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KAFKA-5736) Improve error message in Connect when all kafka brokers are down
[ https://issues.apache.org/jira/browse/KAFKA-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130801#comment-16130801 ] Damian Guy commented on KAFKA-5736: --- [~kkonstantine] is this one necessary for 0.11.0.1? > Improve error message in Connect when all kafka brokers are down > > > Key: KAFKA-5736 > URL: https://issues.apache.org/jira/browse/KAFKA-5736 > Project: Kafka > Issue Type: Bug > Components: KafkaConnect >Affects Versions: 0.11.0.0 >Reporter: Konstantine Karantasis >Assignee: Konstantine Karantasis > Fix For: 0.11.0.1, 1.0.0 > > Original Estimate: 3h > Remaining Estimate: 3h > > Currently when all the Kafka brokers are down, Kafka Connect is failing with > a pretty unintuitive message when it tries to, for instance, reconfigure > tasks. > Example output: > {code:java} > [2017-08-15 19:12:09,959] ERROR Failed to reconfigure connector's tasks, > retrying after backoff: > (org.apache.kafka.connect.runtime.distributed.DistributedHerder) > java.lang.IllegalArgumentException: CircularIterator can only be used on > non-empty lists > at > org.apache.kafka.common.utils.CircularIterator.(CircularIterator.java:29) > at > org.apache.kafka.clients.consumer.RoundRobinAssignor.assign(RoundRobinAssignor.java:61) > at > org.apache.kafka.clients.consumer.internals.AbstractPartitionAssignor.assign(AbstractPartitionAssignor.java:68) > at > ... (connector code) > at > org.apache.kafka.connect.runtime.Worker.connectorTaskConfigs(Worker.java:230) > {code} > The error message needs to be improved, since its root cause is the absence > kafka brokers for assignment. -- This message was sent by Atlassian JIRA (v6.4.14#64029)