Are yo usure your HBase is running? Can you paste the 200 last lines of
your master logs in pastebin?

JM


2014-08-27 3:32 GMT-04:00 Andrey Stepachev <[email protected]>:

> Hi, Praveen.
>
> Can you share more details on HBase version?
> You can look at hbase:namespace table to find out is it enabled and
> deployed somewhere.
> (typically you can find this on master
> http://master:60010/table.jsp?name=hbase:namespace
>
> Andrey.
>
>
> On Wed, Aug 27, 2014 at 10:56 AM, Praveen G <[email protected]> wrote:
>
> > I tried to create a table but it is giving me below error. Kindly check
> >
> > hbase(main):003:0> create 't1', 'f1'
> >
> > ERROR: 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.run(FutureTask.java:262)
> >         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:744)
> >
> > Here is some help for this command:
> > Creates a table. Pass a table name, and a set of column family
> > specifications (at least one), and, optionally, table configuration.
> > Column specification can be a simple string (name), or a dictionary
> > (dictionaries are described below in main help output), necessarily
> > including NAME attribute.
> > Examples:
> >
> >   hbase> create 't1', {NAME => 'f1', VERSIONS => 5}
> >   hbase> create 't1', {NAME => 'f1'}, {NAME => 'f2'}, {NAME => 'f3'}
> >   hbase> # The above in shorthand would be the following:
> >   hbase> create 't1', 'f1', 'f2', 'f3'
> >   hbase> create 't1', {NAME => 'f1', VERSIONS => 1, TTL => 2592000,
> > BLOCKCACHE => true}
> >   hbase> create 't1', {NAME => 'f1', CONFIGURATION =>
> > {'hbase.hstore.blockingStoreFiles' => '10'}}
> >
> > Table configuration options can be put at the end.
> > Examples:
> >
> >   hbase> create 't1', 'f1', SPLITS => ['10', '20', '30', '40']
> >   hbase> create 't1', 'f1', SPLITS_FILE => 'splits.txt', OWNER =>
> 'johndoe'
> >   hbase> create 't1', {NAME => 'f1', VERSIONS => 5}, METADATA => {
> 'mykey'
> > => 'myvalue' }
> >   hbase> # Optionally pre-split the table into NUMREGIONS, using
> >   hbase> # SPLITALGO ("HexStringSplit", "UniformSplit" or classname)
> >   hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO =>
> > 'HexStringSplit'}
> >   hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO =>
> > 'HexStringSplit', REGION_REPLICATION => 2, CONFIGURATION =>
> > {'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}}
> >
> > You can also keep around a reference to the created table:
> >
> >   hbase> t1 = create 't1', 'f1'
> >
> > Which gives you a reference to the table named 't1', on which you can
> then
> > call methods.
> >
> > Br,
> > Praveen G
> >
>
>
>
> --
> Andrey.
>

Reply via email to