Home Forums HDFS Server IPC Version 9

Tagged: 

This topic contains 4 replies, has 4 voices, and was last updated by  Umer Baig 3 hours, 25 minutes ago.

  • Creator
    Topic
  • #43904

    gehhrald
    Member

    Hi,

    I have recently used HDP 2.0 to set up my master and slaves (centOS).
    I’m writing a Java program to be able to interact with the files in the HDFS.
    faced this error and I’m not sure what the problem is:

    org.apache.hadoop.ipc.RemoteException: Server IPC version 9 cannot communicate with client version 4

    Regards,
    Gerald

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

  • Author
    Replies
  • #51611

    Umer Baig
    Participant

    *** Error 7827 Java SQL Exception SQLSTATE 39001: Invalid SQL state ([TD-
    SQLH]: Error serializing hcatalog object: Server IPC version 9 cannot communi
    cate with client version 4).

    I have Hadoop 2.2.0.2.0.6.0-101 and trying to connect with sqlh teradata.

    Collapse
    #44501

    gehhrald
    Member

    Hello Chris and Xiandong,

    Thanks for the information and the help.
    I have updated the referenced libraries in my Java program from the Hadoop-core-1.x.jar to the Hadoop-core-2.x.jar and it worked.
    I guess I forgot to update the referenced libraries while changing from 1.x to 2.x.

    Cheers,
    Gerald

    Collapse
    #44499

    Chris Nauroth
    Participant

    Hello Gerald and Xiandong,

    Between the 1.x line and the 2.x line, there were multiple changes made to the Hadoop RPC interfaces, and these changes are not backwards-compatible. The error message indicates that your application tried to use an older client (likely from the 1.x line) to communicate with a 2.x cluster.

    To fix the problem, you’ll need to link your application with a 2.x Hadoop client. For example, if your project uses Maven for its build, then you can set your Hadoop dependency version to 2.2.0. If you typically run your application from a cluster node using the “hadoop jar” command, then it’s also best to specify provided for Hadoop dependencies. This way, the Maven build will not bundle specific Hadoop jar versions into your build artifacts. Instead, “hadoop jar” will provide its currently deployed version for you.

    Are you in a situation where you need to support an application that can run against either a 1.x cluster or a 2.x cluster? Downstream projects like HBase and Hadoop LZO face this problem, and they solve it by defining separate Maven profiles for linking against 1.x vs. linking against 2.x. If you need to do something similar, then I recommend looking at the pom.xml from Hadoop LZO. That’s probably the simplest example.

    https://github.com/twitter/hadoop-lzo/blob/master/pom.xml

    Hope this helps,
    –Chris

    Collapse
    #44465

    Xiandong Su
    Member

    Gerald, have you resolved this yet? I am running into the exact same error. Some searching online indicating it is some serialization version compatibility issue.

    Collapse
Viewing 4 replies - 1 through 4 (of 4 total)