[
https://issues.apache.org/jira/browse/HBASE-7352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Bertozzi updated HBASE-7352:
-----------------------------------
Attachment: HBASE-7352-v1.patch
What about extracting the wait loop from enableTable() and use that also for
the clone?
{code}
throw new IOException("Unable to enable table " +
Bytes.toString(tableName));
{code}
The enable table code, after N retries says: "Unable to enable table"... but
this looks like the wrong message... we don't know if the enable is failed or
is just slow...
change the message in "table not yet enabled", change the exception type in
RetriesExhaustedException()?
> clone operation from HBaseAdmin can hang forever.
> -------------------------------------------------
>
> Key: HBASE-7352
> URL: https://issues.apache.org/jira/browse/HBASE-7352
> Project: HBase
> Issue Type: Sub-task
> Components: Client, master, regionserver, snapshots, Zookeeper
> Reporter: Jonathan Hsieh
> Assignee: Matteo Bertozzi
> Fix For: hbase-6055, 0.96.0
>
> Attachments: HBASE-7352-v0.patch, HBASE-7352-v1.patch
>
>
> Sometimes the clone operation from the hbase shell can hang. The table has
> been created (it shows up in the web ui), but does not have any entries in
> META.
> There don't seem to be any clone, snapshot, enable or disable found in the
> master's jstack.
> Here's a trace from the HBaseAdmin:
> {code}
> "main" prio=10 tid=0x00007f782800d000 nid=0x25c waiting on condition
> [0x00007f782f9bf000]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.cloneSnapshot(HBaseAdmin.java:2413)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.cloneSnapshot(HBaseAdmin.java:2393)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:465)
> at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:323)
> at
> org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:69)
> at
> org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:201)
> at org.jruby.ast.CallTwoArgNode.interpret(CallTwoArgNode.java:59)
> at org.jruby.ast.NewlineNode.interpret(NewlineNode.java:104)
> ... (more jruby stack) ...
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
