|| at Nov 24, 2010 at 11:45 am
Oh, right, I keep forgetting who is on which version. This was added
in HBASE-3112. So in that case, this is bound by
this.numRetries = conf.getInt("hbase.client.retries.number", 5);
You can up this number in your local config or in your code before
creating the HBaseAdmin connection. Set "hbase.client.retries.number"
to something higher until it works.
On Wed, Nov 24, 2010 at 12:01 PM, Hari Sreekumar
Is the async version available in hbase-0.20.6 ASF version? It is
still in development right?
On Wed, Nov 24, 2010 at 4:09 PM, Lars George wrote:
Disabling a table simply takes time as all RSs need to report back
that the regions are flushed and closed. You may time out on that.
This is where the async, "fire and forget" version of that call comes
in. But if you need to wait you need to use the async and then poll
the status of the table until it is reported as being disabled.
On Wed, Nov 24, 2010 at 7:27 AM, Hari Sreekumar
Update: I see that it usually works when I wait and retry 2-3 times 5 mins.
On Wed, Nov 24, 2010 at 10:08 AM, Hari Sreekumar
What is the cause of this exception? Is there a timeout value that
be modified to avoid this error? Does this error mean any problem with
setup, or is it normal to get these errors? In that case, how can I drop
this table without messing up the cluster? My table has ~40 columns and
Exception in thread "main" org.apache.hadoop.hbase.RegionException:
exhausted, it took too long to wait for the table CustomerData to be
at CreateWebeventTable.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)