[jira] [Updated] (HBASE-6285) HBase master should log INFO message when it attempts to assign a region
[ 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
[ 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] [Updated] (HBASE-6285) HBase master should log INFO message when it attempts to assign a region
[ 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