yes epoll and ulimit -n limits are both upped as suggested by docs. My "test cluster" is pretty typical local dev box, ubuntu 8.10 64bit, sun 1.6, 4G mem, hdfs namenode/datanode hbase master/regionserver all running on the same box. My htable has about 10m rows imported when i hit this state... info pages/logs show all regions are ready but I can't pull any data out from them.
On Sat, May 30, 2009 at 7:48 AM, stack <[email protected]> wrote: > Tell us more about your cluster setup. > > You've upped your file descriptors as per 'Getting Started' doc? > > St.Ack > > On Fri, May 29, 2009 at 7:11 PM, Xinan Wu <[email protected]> wrote: >> >> Hi, >> >> I started to experiment hbase-0.20 trunk code today and imported about >> 6GB data using native JAVA API. I occationally get >> RetriesExhaustedException exception during importing and it's usually >> fixable by restarting everything and resume importing from where it >> stopped last time. But now I am in a state that I can reproduce this >> exception repeatably, even after I completely restart hbase master and >> hdfs master (!).... >> >> After fresh new start, in hbase shell, i can scan '-ROOT-' and >> '.META.', but retrieving value (get) from any other table results >> RetriesExhaustedException exception: >> >> NativeException: >> org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to >> contact region server null for region , row '2', but failed after 5 >> attempts. >> Exceptions: >> org.apache.hadoop.hbase.TableNotFoundException: myTable >> org.apache.hadoop.hbase.TableNotFoundException: myTable >> org.apache.hadoop.hbase.TableNotFoundException: myTable >> org.apache.hadoop.hbase.TableNotFoundException: myTable >> org.apache.hadoop.hbase.TableNotFoundException: myTable >> >> from org/apache/hadoop/hbase/client/HConnectionManager.java:922:in >> `getRegionServerWithRetries' >> from org/apache/hadoop/hbase/client/HTable.java:632:in `getRow' >> ... >> >> issuing 'scan' command of the table just hangs. >> >> Anyone has any idea where I should investigate? The hadoop >> namenode/datanode logs and hbase master/regionserver logs all look >> normal. My table scheme is very simple, single column, everything >> running on the same dev box. >> >> Thanks, > >
