[
https://issues.apache.org/jira/browse/FLINK-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kaicheng Sun updated FLINK-11736:
---------------------------------
Description:
my flink program connect kafka as its sinker using "FlinkKafkaProducer011"
library. But sometimes the flink will exit abnormally with this kind of error:
(2019-02-23 11:55:11,656 WARN
org.apache.kafka.clients.producer.internals.Sender - Got error
produce response with correlation id 55711 on topic-partition
tmp_sink_redis-17, retrying (8 attempts left). Error: NOT_LEADER_FOR_PARTITION
2019-02-23 11:55:11,658 WARN
org.apache.kafka.clients.producer.internals.Sender - Got error
produce response with correlation id 55712 on topic-partition
tmp_sink_redis-17, retrying (8 attempts left). Error: NOT_LEADER_FOR_PARTITION)
The kafka cluster works properly, so I have no idea why this error will happen
was:my flink program connect kafka as its sinker using
"FlinkKafkaProducer011" library. But sometimes the flink will meet with this
kind of error:
> flink kafka producer failed with NOT_LEADER_FOR_PARTITION
> ---------------------------------------------------------
>
> Key: FLINK-11736
> URL: https://issues.apache.org/jira/browse/FLINK-11736
> Project: Flink
> Issue Type: Bug
> Components: Batch Connectors and Input/Output Formats
> Reporter: Kaicheng Sun
> Priority: Major
>
> my flink program connect kafka as its sinker using "FlinkKafkaProducer011"
> library. But sometimes the flink will exit abnormally with this kind of
> error:
> (2019-02-23 11:55:11,656 WARN
> org.apache.kafka.clients.producer.internals.Sender - Got error
> produce response with correlation id 55711 on topic-partition
> tmp_sink_redis-17, retrying (8 attempts left). Error: NOT_LEADER_FOR_PARTITION
> 2019-02-23 11:55:11,658 WARN
> org.apache.kafka.clients.producer.internals.Sender - Got error
> produce response with correlation id 55712 on topic-partition
> tmp_sink_redis-17, retrying (8 attempts left). Error:
> NOT_LEADER_FOR_PARTITION)
>
> The kafka cluster works properly, so I have no idea why this error will happen
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
