[jira] [Updated] (HBASE-6916) HBA logs at info level errors that won't show in the shell

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

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

stack updated HBASE-6916:
-------------------------

    Fix Version/s:     (was: 0.95.0)
                   0.94.2

Fix up after bulk move overwrote some 0.94.2 fix versions w/ 0.95.0 (Noticed by Lars Hofhansl)
                
> HBA logs at info level errors that won't show in the shell
> ----------------------------------------------------------
>
>                 Key: HBASE-6916
>                 URL: https://issues.apache.org/jira/browse/HBASE-6916
>             Project: HBase
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 0.90.6, 0.92.1, 0.94.1, 0.95.2
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Minor
>             Fix For: 0.94.2
>
>         Attachments: HBASE-6916-0.94.patch, HBASE-6916.patch, HBASE-6916-v2.patch
>
>
> There is a weird interaction between the shell and HBA. When you try to close a region that doesn't exist, it doesn't throw any error:
> {noformat}
> hbase(main):029:0> close_region 'thisisaninvalidregion'
> 0 row(s) in 0.0580 seconds
> {noformat}
> Normally one should get UnknownRegionException. Starting the shell with "-d" I see what a non-shell user would see along with a ton of logging from ZK (skipped here):
> {noformat}
> INFO client.HBaseAdmin: No server in .META. for thisisaninvalidregion; pair=null
> {noformat}
> But again this is not the right message, it should have shown
> {noformat}
> INFO client.HBaseAdmin: No server in .META. for thisisaninvalidregion; pair=null
> {noformat}
> And this is because that part of the code treats both UnknownRegionException and NoServerForRegionException like if it was the same thing.
> There is also some ugliness in flush, compact, and split but it normally doesn't show since the code treats everything like it's a table and sends a TableNotFoundException.
> This jira is about making sure that the exceptions are correctly coming out.

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