I got a lot of these disconnection error logs. Why? My flink and kafka
clusters are running in Google Cloud and I dont think there is a network
issue. Also I got this error even my workload is very low.

2023-08-01 21:54:00,003 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Producer clientId=producer-7] Node -1 disconnected.
2023-08-01 21:54:00,003 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Producer clientId=producer-15] Node -1 disconnected.
2023-08-01 21:54:00,004 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Producer clientId=producer-3] Node -1 disconnected.
2023-08-01 21:54:00,108 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Producer clientId=producer-39] Node -1 disconnected.
2023-08-01 21:54:00,109 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Producer clientId=producer-11] Node -1 disconnected.
2023-08-01 21:54:03,000 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Producer clientId=producer-18] Node -1 disconnected.
2023-08-01 21:54:05,128 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Consumer clientId=cpu_46330-9,
groupId=cpualgosgroup1] Disconnecting from node 2 due to request timeout.
2023-08-01 21:54:05,128 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Consumer clientId=cpu_46330-9,
groupId=cpualgosgroup1] Cancelled in-flight FETCH request with correlation
id 3774321 due to node 2 being disconnected (elapsed time since creation:
38505ms, elapsed time since send: 38505ms, request timeout: 30000ms)
2023-08-01 21:54:05,128 INFO  org.apache.kafka.clients.FetchSessionHandler
                [] - [Consumer clientId=cpu_46330-9,
groupId=cpualgosgroup1] Error sending fetch request (sessionId=661615761,
epoch=1) to node 2:
org.apache.kafka.common.errors.DisconnectException: null
2023-08-01 21:54:09,198 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Consumer clientId=cpu_46330-7,
groupId=cpualgosgroup1] Disconnecting from node 1 due to request timeout.
2023-08-01 21:54:09,198 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Consumer clientId=cpu_46330-7,
groupId=cpualgosgroup1] Cancelled in-flight FETCH request with correlation
id 6902407 due to node 1 being disconnected (elapsed time since creation:
38677ms, elapsed time since send: 38677ms, request timeout: 30000ms)
2023-08-01 21:54:09,198 INFO  org.apache.kafka.clients.FetchSessionHandler
                [] - [Consumer clientId=cpu_46330-7,
groupId=cpualgosgroup1] Error sending fetch request (sessionId=1602736870,
epoch=1) to node 1:
org.apache.kafka.common.errors.DisconnectException: null
2023-08-01 21:54:10,425 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Producer clientId=producer-12] Node -1 disconnected.
2023-08-01 21:54:10,427 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Producer clientId=producer-45] Node -1 disconnected.
2023-08-01 21:54:19,148 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Consumer clientId=cpu_46330-2,
groupId=cpualgosgroup1] Disconnecting from node 2 due to request timeout.
2023-08-01 21:54:19,148 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Consumer clientId=cpu_46330-2,
groupId=cpualgosgroup1] Cancelled in-flight FETCH request with correlation
id 7250900 due to node 2 being disconnected (elapsed time since creation:
41074ms, elapsed time since send: 41073ms, request timeout: 30000ms)
2023-08-01 21:54:19,148 INFO  org.apache.kafka.clients.FetchSessionHandler
                [] - [Consumer clientId=cpu_46330-2,
groupId=cpualgosgroup1] Error sending fetch request (sessionId=151959173,
epoch=INITIAL) to node 2:
org.apache.kafka.common.errors.DisconnectException: null
2023-08-01 21:59:00,002 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Producer clientId=producer-27] Node 2 disconnected.
2023-08-01 21:59:00,003 INFO  org.apache.kafka.clients.NetworkClient
                [] - [Producer clientId=producer-13] Node 2 disconnected.

Reply via email to