You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2012/10/02 03:37:07 UTC
[jira] [Created] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Jean-Daniel Cryans created HBASE-6916:
-----------------------------------------
Summary: 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.94.1, 0.92.1, 0.90.6, 0.96.0
Reporter: Jean-Daniel Cryans
Priority: Minor
Fix For: 0.90.7, 0.92.2, 0.94.3, 0.96.0
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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469942#comment-13469942 ]
Hudson commented on HBASE-6916:
-------------------------------
Integrated in HBase-0.94-security #59 (See [https://builds.apache.org/job/HBase-0.94-security/59/])
HBASE-6916 HBA logs at info level errors that won't show in the shell (Revision 1394272)
Result = FAILURE
jdcryans :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* /hbase/branches/0.94/src/test/ruby/hbase/admin_test.rb
> 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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469085#comment-13469085 ]
Hadoop QA commented on HBASE-6916:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12547649/HBASE-6916-v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 83 warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.security.token.TestZKSecretWatcher
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/3000//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3000//console
This message is automatically generated.
> 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.2, 0.94.3, 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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Jimmy Xiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468988#comment-13468988 ]
Jimmy Xiang commented on HBASE-6916:
------------------------------------
+1
> 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.2, 0.94.3, 0.96.0
>
> Attachments: HBASE-6916-0.94.patch, HBASE-6916.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
[jira] [Updated] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans updated HBASE-6916:
--------------------------------------
Fix Version/s: (was: 0.90.7)
Assignee: Jean-Daniel Cryans
Status: Patch Available (was: Open)
> 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.94.1, 0.92.1, 0.90.6, 0.96.0
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Priority: Minor
> Fix For: 0.94.3, 0.96.0, 0.92.2
>
> Attachments: HBASE-6916-0.94.patch, HBASE-6916.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
[jira] [Updated] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans updated HBASE-6916:
--------------------------------------
Attachment: HBASE-6916-v2.patch
In this new patch I removed the close_region test since it's broken and I can't think of a nice way to get a full region name in there.
> 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.2, 0.94.3, 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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469808#comment-13469808 ]
Hudson commented on HBASE-6916:
-------------------------------
Integrated in HBase-TRUNK #3426 (See [https://builds.apache.org/job/HBase-TRUNK/3426/])
HBASE-6916 HBA logs at info level errors that won't show in the shell (Revision 1394274)
Result = FAILURE
jdcryans :
Files :
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* /hbase/trunk/hbase-server/src/test/ruby/hbase/admin_test.rb
> 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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469990#comment-13469990 ]
Hudson commented on HBASE-6916:
-------------------------------
Integrated in HBase-0.92-security #143 (See [https://builds.apache.org/job/HBase-0.92-security/143/])
HBASE-6916 HBA logs at info level errors that won't show in the shell (Revision 1394271)
Result = FAILURE
jdcryans :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* /hbase/branches/0.92/src/test/ruby/hbase/admin_test.rb
> 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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469042#comment-13469042 ]
Jean-Daniel Cryans commented on HBASE-6916:
-------------------------------------------
The TestShell failure is legit, it's always been failing but silently:
{noformat}
Wed Oct 3 23:45:04 UTC 2012......Finished in 72.002 seconds. 1) Error:
test_close_should_work_without_region_server_name(Hbase::AdminMethodsTest):
NativeException: org.apache.hadoop.hbase.UnknownRegionException: hbase_create_table_test_table,,0
org/apache/hadoop/hbase/client/HBaseAdmin.java:1115:in `closeRegion'
{noformat}
That region name doesn't exist, it's bogus.
The other ones seem unrelated.
> 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.2, 0.94.3, 0.96.0
>
> Attachments: HBASE-6916-0.94.patch, HBASE-6916.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
[jira] [Updated] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans updated HBASE-6916:
--------------------------------------
Attachment: HBASE-6916-0.94.patch
Attaching a patch that simply replaces the LOG.info statements with exceptions that are thrown. It also fixes the logic in closeRegion.
Now I see:
{noformat}
hbase(main):001:0> close_region 'thisisaninvalidregion'
2012-10-01 18:27:51.595 java[29064:1203]
ERROR: org.apache.hadoop.hbase.UnknownRegionException: thisisaninvalidregion
{noformat}
> 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
> Priority: Minor
> Fix For: 0.90.7, 0.92.2, 0.94.3, 0.96.0
>
> Attachments: HBASE-6916-0.94.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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Elliott Clark (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469717#comment-13469717 ]
Elliott Clark commented on HBASE-6916:
--------------------------------------
+1 lgtm
> 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.2, 0.94.3, 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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469027#comment-13469027 ]
Hadoop QA commented on HBASE-6916:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12547626/HBASE-6916.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 83 warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor
org.apache.hadoop.hbase.client.TestShell
org.apache.hadoop.hbase.regionserver.wal.TestHLog
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2998//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2998//console
This message is automatically generated.
> 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.2, 0.94.3, 0.96.0
>
> Attachments: HBASE-6916-0.94.patch, HBASE-6916.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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469843#comment-13469843 ]
Hudson commented on HBASE-6916:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #209 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/209/])
HBASE-6916 HBA logs at info level errors that won't show in the shell (Revision 1394274)
Result = FAILURE
jdcryans :
Files :
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* /hbase/trunk/hbase-server/src/test/ruby/hbase/admin_test.rb
> 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
[jira] [Updated] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans updated HBASE-6916:
--------------------------------------
Attachment: HBASE-6916.patch
Attaching the trunk patch.
> 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
> Priority: Minor
> Fix For: 0.92.2, 0.94.3, 0.96.0
>
> Attachments: HBASE-6916-0.94.patch, HBASE-6916.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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469861#comment-13469861 ]
Hudson commented on HBASE-6916:
-------------------------------
Integrated in HBase-0.92 #594 (See [https://builds.apache.org/job/HBase-0.92/594/])
HBASE-6916 HBA logs at info level errors that won't show in the shell (Revision 1394271)
Result = SUCCESS
jdcryans :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* /hbase/branches/0.92/src/test/ruby/hbase/admin_test.rb
> 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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469899#comment-13469899 ]
Hudson commented on HBASE-6916:
-------------------------------
Integrated in HBase-0.94-security-on-Hadoop-23 #8 (See [https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/8/])
HBASE-6916 HBA logs at info level errors that won't show in the shell (Revision 1394272)
Result = FAILURE
jdcryans :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* /hbase/branches/0.94/src/test/ruby/hbase/admin_test.rb
> 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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469797#comment-13469797 ]
Lars Hofhansl commented on HBASE-6916:
--------------------------------------
bq. +1 on commit. Put in 0.94 to make Lars happy.
That made me happy ;)
> 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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467437#comment-13467437 ]
stack commented on HBASE-6916:
------------------------------
+1 on commit. Put in 0.94 to make Lars happy.
> 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
> Priority: Minor
> Fix For: 0.90.7, 0.92.2, 0.94.3, 0.96.0
>
> Attachments: HBASE-6916-0.94.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
[jira] [Commented] (HBASE-6916) HBA logs at info level errors that
won't show in the shell
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469791#comment-13469791 ]
Hudson commented on HBASE-6916:
-------------------------------
Integrated in HBase-0.94 #505 (See [https://builds.apache.org/job/HBase-0.94/505/])
HBASE-6916 HBA logs at info level errors that won't show in the shell (Revision 1394272)
Result = FAILURE
jdcryans :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* /hbase/branches/0.94/src/test/ruby/hbase/admin_test.rb
> 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