java.io.EOFException: Premature EOF: no length prefix available

cloudera.com | 4 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Solved: Re: data nodes evicted randomly and cluster marks ... - Cloudera Community

    cloudera.com | 4 months ago
    java.io.EOFException: Premature EOF: no length prefix available
  2. 0

    regionserver crash after node decomission

    Google Groups | 3 years ago | Ian Brooks
    java.io.EOFException: Premature EOF: no length prefix available
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    Re: regionserver crash after node decomission

    apache.org | 1 year ago
    java.io.EOFException: Premature EOF: no length prefix available

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.EOFException

      Premature EOF: no length prefix available

      at org.apache.hadoop.hdfs.protocolPB.PBHelper.vintPrefixed()
    2. Apache Hadoop HDFS
      BlockReceiver$PacketResponder.run
      1. org.apache.hadoop.hdfs.protocolPB.PBHelper.vintPrefixed(PBHelper.java:1988)
      2. org.apache.hadoop.hdfs.protocol.datatransfer.PipelineAck.readFields(PipelineAck.java:176)
      3. org.apache.hadoop.hdfs.server.datanode.BlockReceiver$PacketResponder.run(BlockReceiver.java:1083)
      3 frames
    3. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:744)
      1 frame