Home Forums HDP on Windows – Installation hdp 2.0 installed on windows successfuly but hbase shows 9095 port conflict

This topic contains 3 replies, has 2 voices, and was last updated by  Dave 6 months ago.

  • Creator
    Topic
  • #48775

    Harish Bansal
    Participant

    Hi,

    We have installed hdp 2.0 on 4 64 bit windows 7 boxes successfuly and Hive is working well. Hbase Master is configured on one boxes and region server on rest of the 3 windows 7 boxes. on Master machine. But Hbase is not starting and not able to connect with region servers. Follwoing is the error logs from hbase master and thrift 2: We are running services as hadoop user.

    Hbase Master

    INFO org.apache.zookeeper.ZooKeeper: Initiating client connection, connectString=ServerSANDBOX04:2181,ServerHADOOP:2181,ServerSANDBOX05:2181 sessionTimeout=90000 watcher=master:60000
    INFO org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Process identifier=master:60000 connecting to ZooKeeper ensemble=ServerSANDBOX04:2181,ServerHADOOP:2181,ServerSANDBOX05:2181
    INFO org.apache.zookeeper.ClientCnxn: Opening socket connection to server Serversandbox04.mybox.com/192.xxx.20.xxx:2181. Will not attempt to authenticate using SASL (unknown error)
    INFO org.apache.zookeeper.ClientCnxn: Socket connection established to Serversandbox04.mybox.com/192.xxx.20.xxx:2181, initiating session
    INFO org.apache.zookeeper.ClientCnxn: Unable to read additional data from server sessionid 0×0, likely server has closed socket, closing socket connection and attempting reconnect
    WARN org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Possibly transient ZooKeeper, quorum=ServerSANDBOX04:2181,ServerHADOOP:2181,ServerSANDBOX05:2181, exception=org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase
    INFO org.apache.hadoop.hbase.util.RetryCounter: Sleeping 2000ms before retry #1…
    INFO org.apache.zookeeper.ClientCnxn: Opening socket connection to server ServerHADOOP.mybox.com/192.xxx.20.xxx:2181. Will not attempt to authenticate using SASL (unknown error)

    Thrift 2
    INFO org.apache.hadoop.http.HttpServer: HttpServer.start() threw a non Bind IOException java.net.BindException: Port in use: 0.0.0.0:9095
    at org.apache.hadoop.http.HttpServer.openListener(HttpServer.java:742)
    at org.apache.hadoop.http.HttpServer.start(HttpServer.java:686)
    at org.apache.hadoop.hbase.thrift2.ThriftServer.main(ThriftServer.java:302)

    On verification of pofts and processes, 9095 is with Hadoop processes only. In services list, Hbase master, rest and Thrift services are starting alternatively.

    Please guide about solution.

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

You must be logged in to reply to this topic.

  • Author
    Replies
  • #49417

    Dave
    Moderator

    Hi Harish,

    If you run netstat and look for 9095 & 9090 – are the ports actually in use?

    Thanks

    Dave

    Collapse
    #48833

    Harish Bansal
    Participant

    Hi Dave,

    Thanks for your help, its much appreciated.

    Hbase has started working on our server. But Hbase thrift and thrift2 are still in conflict. Following are the logs from both of these:

    hbase-thrift-ServerHADOOP.log
    org.mortbay.log: Started SelectChannelConnector@0.0.0.0:9095
    org.apache.hadoop.hbase.thrift.ThriftServerRunner: starting TBoundedThreadPoolServer on /0.0.0.0:9090; min worker threads=16, max worker threads=1000, max queued requests=1000

    hbase-thrift2-ServerHADOOP.log
    ERROR org.apache.hadoop.hbase.thrift2.ThriftServer: Port in use: 0.0.0.0:9095
    java.net.BindException: Port in use: 0.0.0.0:9095

    Collapse
    #48781

    Dave
    Moderator

    Hi Harish,

    Can you confirm you can reach your zookeeper nodes from the HBase Master machine?
    Please ensure that local firewall rules on the Windows machines all allow connectivity (test with Telnet) This will be from HBase Master machine to ServerHadoop, ServerSANDBOX05, ServerSANDBOX04 on port 2181
    Ensure that the Thrift server can run on port 9095 – stop the service, do a netstat -an | find “9095″ (ensure it is not listening – if it is then kill off the process and start the thrift server again)

    Thanks

    Dave

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