You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/11/11 21:07:14 UTC
[jira] Updated: (HBASE-3229) Table creation, though using "async"
call to master, can actually run for a while and cause RPC timeout
[ https://issues.apache.org/jira/browse/HBASE-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-3229:
-------------------------
Fix Version/s: (was: 0.90.0)
0.92.0
> Table creation, though using "async" call to master, can actually run for a while and cause RPC timeout
> -------------------------------------------------------------------------------------------------------
>
> Key: HBASE-3229
> URL: https://issues.apache.org/jira/browse/HBASE-3229
> Project: HBase
> Issue Type: Bug
> Components: client, master
> Affects Versions: 0.90.0
> Reporter: Jonathan Gray
> Priority: Critical
> Fix For: 0.92.0
>
>
> Our create table methods in HBaseAdmin are synchronous from client POV. However, underneath, we're using an "async" create and then looping waiting for table availability. Because the create is async and we loop instead of block on RPC, we don't expect RPC timeouts.
> However, when creating a table with lots of initial regions, the "async" create can actually take a long time (more than 30 seconds in this case) which causes the client to timeout and gives impression something failed.
> We should make the create truly async so that this can't happen. And rather than doing one-off, inline assignment as it is today, we should reuse the fancy enable/disable code stack just added to make this faster and more optimal.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.