[jira] Commented: (HBASE-3650) HBA.delete can return too fast

["stack (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007285#comment-13007285 ] 

stack commented on HBASE-3650:
------------------------------

Do we allow tables w/ '+' in their name?  Or anything < ','?

THere is a system.out that you probably want to remove on commit.

Add javadoc to this method, +  public static Scan getScanForTableName(byte[] tableName) {, since its going to be come really popular really quickly.

+1

> 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.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