Home Forums HBase org.apache.hadoop.hbase.client.RpcRetryingCaller in hbase/phoenix

Tagged: 

This topic contains 2 replies, has 3 voices, and was last updated by  Andrew Grande 3 months, 1 week ago.

  • Creator
    Topic
  • #52554

    Very Test
    Participant

    Hello
    Following the PDF provided by HDP (bk_installing_manually_book-20140422.pdf), I got an exception when running:

    ./psql.py localhost /usr/share/doc/phoenix-4.0.0.2.1.1.0/examples/WEB_STAT.sql /usr/share/doc/phoenix-4.0.0.2.1.1.0/examples/WEB_STAT.csv /usr/share/doc/phoenix-4.0.0.2.1.1.0/examples/WEB_STAT_QUERIES.sql
    
    Tue Apr 29 17:26:44 UTC 2014, org.apache.hadoop.hbase.client.RpcRetryingCaller@65072974, org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(java.io.IOException): java.io.IOException: Table Namespace Manager not ready yet, try again later
    	at org.apache.hadoop.hbase.master.HMaster.getNamespaceDescriptor(HMaster.java:3205)
    	at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1730)
    	at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1860)
    	at org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:38221)
    	at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2008)
    	at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:92)
    	at org.apache.hadoop.hbase.ipc.FifoRpcScheduler$1.run(FifoRpcScheduler.java:73)
    	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    	at java.lang.Thread.run(Thread.java:724)
    

    What does that means ? The others checks in this PDF are correct.

    Regards

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

You must be logged in to reply to this topic.

  • Author
    Replies
  • #56339

    Andrew Grande
    Participant

    Hi, there probably was a typo in the phoenix core jar path, make sure that you symlink to a valid file. After you do this, check the hbase regionserver startup logs (/usr/lib/hbase/logs). If the issue is still there, try copying the file physically into /usr/lib/hbase/lib instead of symlinking.

    We’re fixing the docs to reflect changes as we speak.

    Collapse
    #54434

    Neeraj Garg
    Participant

    Hi,

    We’ve been facing the same issue in HBase 0.98. We’ve been using HDP 2.1 distribution over 8 nodes cluster.

    Could somebody quickly post the resolution.

    Thank you in advance,
    Neeraj

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