[jira] Updated: (HBASE-510) HConnectionManger.listTables returns empty list if exception (though there may be many tables present)

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

     [ https://issues.apache.org/jira/browse/HBASE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Duxbury updated HBASE-510:
--------------------------------

    Attachment: 510-0.1.patch

Patch for 0.1 that adds retry logic around the listTables scan code. Passes unit tests.

> HConnectionManger.listTables returns empty list if exception (though there may be many tables present)
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-510
>                 URL: https://issues.apache.org/jira/browse/HBASE-510
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.1.0, 0.2.0, 0.16.0
>            Reporter: stack
>            Assignee: Bryan Duxbury
>            Priority: Minor
>             Fix For: 0.1.0
>
>         Attachments: 510-0.1.patch
>
>
> Its a problem because commonly a check for existence will get list of current tables.
> Yesterday saw problem when .META. went off line.  A piece of client code was asking for list of tables when .META. was offline, it was getting back an empty list because listTables do while was seeing 'org.apache.hadoop.hbase.NotServingRegionException: .META.,,1'
> Problem is the do while in HCM.listTables goes as long as startRow does not equal LAST_ROW but startRow is initialized with EMPTY_START_ROW which is equal to LAST_ROW.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.