[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans updated HBASE-6916: -------------------------------------- Resolution: Fixed Fix Version/s: (was: 0.94.3) (was: 0.92.2) 0.94.2 0.92.3 Release Note: The close_region shell command won't fail silently anymore, code relying on this behavior will now get UnknownRegionException Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to .92, .94, and trunk. Thanks for the reviews guys. > 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.96.0 > Reporter: Jean-Daniel Cryans > Assignee: Jean-Daniel Cryans > Priority: Minor > Fix For: 0.92.3, 0.94.2, 0.96.0 > > 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