[
https://issues.apache.org/jira/browse/HBASE-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007480#comment-13007480
]
Jean-Daniel Cryans commented on HBASE-3650:
-------------------------------------------
All the unit tests are passing with this patch:
{quote}
Tests run: 629, Failures: 0, Errors: 0, Skipped: 9
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 82 minutes 37 seconds
[INFO] Finished at: Tue Mar 15 23:36:03 PDT 2011
[INFO] Final Memory: 63M/123M
[INFO] ------------------------------------------------------------------------
{quote}
> HBA.delete can return too fast
> ------------------------------
>
> Key: HBASE-3650
> URL: https://issues.apache.org/jira/browse/HBASE-3650
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.1
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Priority: Blocker
> Fix For: 0.90.2
>
> Attachments: HBASE-3650-v2.patch, HBASE-3650.patch
>
>
> One of our engineers got a weird TableExistsException in his code and I see
> that the client-side logging says the table was deleted in less than a second
> while it took the master 5 seconds to do it. Doing code inspection, the
> .META. scanner in HBA.delete can set _found_ to _true_ and then set it back
> to _false_ in the case where the deleted table isn't the last one. We should
> just do a scan that would get the rows specific to the table instead of
> scanning *all* the rows.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
