Hi Team, I am deploying my job in application mode...
# troubleshooting
a
Hi Team, I am deploying my job in application mode on Flink-1.16.0, but keep constantly receiving this error from a long time:
Copy code
2023-04-10 13:48:39,366 INFO  org.apache.kafka.clients.NetworkClient                       [] - [Consumer clientId=event-executor-client-1, groupId=event-executor-grp] Node 1 disconnected.
2023-04-10 13:48:39,366 INFO  org.apache.kafka.clients.NetworkClient                       [] - [Consumer clientId=event-executor-client-1, groupId=event-executor-grp] Cancelled in-flight FETCH request with correlation id 8759 due to node 1 being disconnected (elapsed time since creation: 0ms, elapsed time since send: 0ms, request timeout: 30000ms)
2023-04-10 13:48:39,366 INFO  org.apache.kafka.clients.FetchSessionHandler                 [] - [Consumer clientId=event-executor-client-1, groupId=event-executor-grp] Error sending fetch request (sessionId=INVALID, epoch=INITIAL) to node 1:
org.apache.kafka.common.errors.DisconnectException: null
2023-04-10 13:48:40,317 INFO  org.apache.kafka.clients.NetworkClient                       [] - [Producer clientId=producer-122] Node 19 disconnected.
2023-04-10 13:51:20,059 INFO  org.apache.kafka.clients.NetworkClient                       [] - [Consumer clientId=event-executor-client-1, groupId=event-executor-grp] Node 16 disconnected.
2023-04-10 13:51:20,060 INFO  org.apache.kafka.clients.NetworkClient                       [] - [Consumer clientId=event-executor-client-1, groupId=event-executor-grp] Cancelled in-flight FETCH request with correlation id 10312 due to node 16 being disconnected (elapsed time since creation: 0ms, elapsed time since send: 0ms, request timeout: 30000ms)
2023-04-10 13:51:20,060 INFO  org.apache.kafka.clients.FetchSessionHandler                 [] - [Consumer clientId=event-executor-client-1, groupId=event-executor-grp] Error sending fetch request (sessionId=INVALID, epoch=INITIAL) to node 16:
org.apache.kafka.common.errors.DisconnectException: null
2023-04-10 13:51:48,469 WARN  org.apache.flink.connector.kafka.source.reader.KafkaSourceReader [] - Failed to commit consumer offsets for checkpoint 4
org.apache.kafka.clients.consumer.RetriableCommitFailedException: Offset commit failed with a retriable exception. You should retry committing the latest consumed offsets.
Caused by: org.apache.kafka.common.errors.CoordinatorNotAvailableException: The coordinator is not available.
2023-04-10 13:51:48,829 WARN  org.apache.flink.connector.kafka.source.reader.KafkaSourceReader [] - Failed to commit consumer offsets for checkpoint 4
org.apache.kafka.clients.consumer.RetriableCommitFailedException: Offset commit failed with a retriable exception. You should retry committing the latest consumed offsets.
Caused by: org.apache.kafka.common.errors.CoordinatorNotAvailableException: The coordinator is not available.
Also, found this ticket with the above issue: https://issues.apache.org/jira/browse/FLINK-27962?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel Seems the issue is still not resolved. If anyone knows how to solve this issue, please help.Thanks
m
It can’t be the same ticket, because that’s for an older Flink version. The new one has a fix for that
a
Which Version has the fix?
If there’s a jira ticket for same issue on flink1.16.0, can you please share that as well. Thanks
p
Experiencing the same issue with pyflink 1.16.1. Only seems to occur when i have a lookup join cache.