You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "jinshaoling (Jira)" <ji...@apache.org> on 2020/06/03 03:28:00 UTC

[jira] [Created] (KAFKA-10088) The ephemeral node [%s] at %s has gone away while reading it

jinshaoling created KAFKA-10088:
-----------------------------------

             Summary: The ephemeral node [%s] at %s has gone away while reading it
                 Key: KAFKA-10088
                 URL: https://issues.apache.org/jira/browse/KAFKA-10088
             Project: Kafka
          Issue Type: Improvement
          Components: core
    Affects Versions: 0.10.2.3
         Environment: Linux 3.10.0-693.2.2.el7.x86_64
            Reporter: jinshaoling
         Attachments: 1DF600B6-388B-4cd3-800F-93AD39323C3E.png

I use kafka 10.0.2 in the production environment, and a problem occurs: the problem should be after the re-election of the controller. due to the relatively large amount of data, the log is soon filled, and soon the alarm of insufficient disk space appears . The log level used in our production environment is "info", and the log is like this:
{code:java}
 The ephemeral node [***] at *** has gone away while reading it {code}
I downloaded the source code of kafka from github and found in kafka.utils.ZkUtils
CreateCallback#: 
 
{code:java}
case Code.NODEEXISTS =>    zkHandle.getData(path, false, getDataCallback, null) {code}
 
GetDataCallback#: 
{code:java}
case Code.NONODE => info("The ephemeral node [%s] at %s has gone away while reading it, ".format(data, path)) {code}
 
one case is Code.NODEEXISTS , but another case is  Code.NONODE. I think this problem should come from zookeeper, but I don’t know why?
Please help me, thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)