You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Aditya Kishore (JIRA)" <ji...@apache.org> on 2012/06/27 23:24:43 UTC
[jira] [Created] (HBASE-6285) HBase master should log INFO message
when it attempts to assign a region
Aditya Kishore created HBASE-6285:
-------------------------------------
Summary: HBase master should log INFO message when it attempts to assign a region
Key: HBASE-6285
URL: https://issues.apache.org/jira/browse/HBASE-6285
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.94.0
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Priority: Minor
With the default logging level (INFO), it is very difficult to diagnose a large HBase cluster that is having problems assigning regions because the HBase master logs a DEBUG message when it instructs a region-server to assign a region.
You actually have to crawl EVERY HBase region-server log to find out which node received the request for a particular region. Further, lets say the HBase master sends the request and something goes wrong, we might not even get a message in the region-server log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6285) HBase master should log INFO
message when it attempts to assign a region
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403478#comment-13403478 ]
Hadoop QA commented on HBASE-6285:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12533708/HBASE-6285_trunk.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. 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.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to introduce 6 new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestAtomicOperation
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2285//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2285//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2285//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2285//console
This message is automatically generated.
> HBase master should log INFO message when it attempts to assign a region
> ------------------------------------------------------------------------
>
> Key: HBASE-6285
> URL: https://issues.apache.org/jira/browse/HBASE-6285
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.94.0
> Reporter: Aditya Kishore
> Assignee: Aditya Kishore
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: HBASE-6285_trunk.patch
>
>
> With the default logging level (INFO), it is very difficult to diagnose a large HBase cluster that is having problems assigning regions because the HBase master logs a DEBUG message when it instructs a region-server to assign a region.
> You actually have to crawl EVERY HBase region-server log to find out which node received the request for a particular region. Further, lets say the HBase master sends the request and something goes wrong, we might not even get a message in the region-server log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6285) HBase master should log INFO
message when it attempts to assign a region
Posted by "Aditya Kishore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403541#comment-13403541 ]
Aditya Kishore commented on HBASE-6285:
---------------------------------------
The test failures are unrelated to the patch.
> HBase master should log INFO message when it attempts to assign a region
> ------------------------------------------------------------------------
>
> Key: HBASE-6285
> URL: https://issues.apache.org/jira/browse/HBASE-6285
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.94.0
> Reporter: Aditya Kishore
> Assignee: Aditya Kishore
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: HBASE-6285_trunk.patch
>
>
> With the default logging level (INFO), it is very difficult to diagnose a large HBase cluster that is having problems assigning regions because the HBase master logs a DEBUG message when it instructs a region-server to assign a region.
> You actually have to crawl EVERY HBase region-server log to find out which node received the request for a particular region. Further, lets say the HBase master sends the request and something goes wrong, we might not even get a message in the region-server log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6285) HBase master should log INFO message
when it attempts to assign a region
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-6285:
-------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk. Thanks for the patch Aditya.
> HBase master should log INFO message when it attempts to assign a region
> ------------------------------------------------------------------------
>
> Key: HBASE-6285
> URL: https://issues.apache.org/jira/browse/HBASE-6285
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.94.0
> Reporter: Aditya Kishore
> Assignee: Aditya Kishore
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: HBASE-6285_trunk.patch
>
>
> With the default logging level (INFO), it is very difficult to diagnose a large HBase cluster that is having problems assigning regions because the HBase master logs a DEBUG message when it instructs a region-server to assign a region.
> You actually have to crawl EVERY HBase region-server log to find out which node received the request for a particular region. Further, lets say the HBase master sends the request and something goes wrong, we might not even get a message in the region-server log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6285) HBase master should log INFO message
when it attempts to assign a region
Posted by "Aditya Kishore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aditya Kishore updated HBASE-6285:
----------------------------------
Fix Version/s: 0.96.0
Status: Patch Available (was: Open)
The attached patch is for trunk.
> HBase master should log INFO message when it attempts to assign a region
> ------------------------------------------------------------------------
>
> Key: HBASE-6285
> URL: https://issues.apache.org/jira/browse/HBASE-6285
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.94.0
> Reporter: Aditya Kishore
> Assignee: Aditya Kishore
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: HBASE-6285_trunk.patch
>
>
> With the default logging level (INFO), it is very difficult to diagnose a large HBase cluster that is having problems assigning regions because the HBase master logs a DEBUG message when it instructs a region-server to assign a region.
> You actually have to crawl EVERY HBase region-server log to find out which node received the request for a particular region. Further, lets say the HBase master sends the request and something goes wrong, we might not even get a message in the region-server log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6285) HBase master should log INFO
message when it attempts to assign a region
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405789#comment-13405789 ]
Hudson commented on HBASE-6285:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #78 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/78/])
HBASE-6285 HBase master should log INFO message when it attempts to assign a region (Revision 1356247)
Result = FAILURE
stack :
Files :
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
> HBase master should log INFO message when it attempts to assign a region
> ------------------------------------------------------------------------
>
> Key: HBASE-6285
> URL: https://issues.apache.org/jira/browse/HBASE-6285
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.94.0
> Reporter: Aditya Kishore
> Assignee: Aditya Kishore
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: HBASE-6285_trunk.patch
>
>
> With the default logging level (INFO), it is very difficult to diagnose a large HBase cluster that is having problems assigning regions because the HBase master logs a DEBUG message when it instructs a region-server to assign a region.
> You actually have to crawl EVERY HBase region-server log to find out which node received the request for a particular region. Further, lets say the HBase master sends the request and something goes wrong, we might not even get a message in the region-server log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6285) HBase master should log INFO message
when it attempts to assign a region
Posted by "Aditya Kishore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aditya Kishore updated HBASE-6285:
----------------------------------
Attachment: HBASE-6285_trunk.patch
Patch for trunk with existing DEBUG log message changed to INFO.
> HBase master should log INFO message when it attempts to assign a region
> ------------------------------------------------------------------------
>
> Key: HBASE-6285
> URL: https://issues.apache.org/jira/browse/HBASE-6285
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.94.0
> Reporter: Aditya Kishore
> Assignee: Aditya Kishore
> Priority: Minor
> Attachments: HBASE-6285_trunk.patch
>
>
> With the default logging level (INFO), it is very difficult to diagnose a large HBase cluster that is having problems assigning regions because the HBase master logs a DEBUG message when it instructs a region-server to assign a region.
> You actually have to crawl EVERY HBase region-server log to find out which node received the request for a particular region. Further, lets say the HBase master sends the request and something goes wrong, we might not even get a message in the region-server log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira