Help Center/ Distributed Message Service for Kafka/ Troubleshooting/ Flink 1.15 Consumption Progress Submission Failure

Updated on 2024-11-20 GMT+08:00

View PDF

Flink 1.15 Consumption Progress Submission Failure

Symptom

To consume Kafka messages in Flink 1.15, the consumption progress fails to be submitted, and the error messages "COORDINATOR_NOT_AVAILABLE" are thrown.

Root Cause

Bug on the Kafka client used by Flink 1.15: When the consumption progress fails to be submitted for once, the client sets the coordinator to unavailable and it cannot be automatically restored.

Solution

Restart the Flink job.
Upgrade Flink to 1.16 or later.

Previous topic: Troubleshooting Error "Topic {{topic_name}} not present in metadata after 60000 ms" During Message Production or Consumption

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.