You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/08/29 08:51:37 UTC

[jira] [Created] (HBASE-4276) AssignmentManager debug logs should be at INFO level for META/ROOT regions

AssignmentManager debug logs should be at INFO level for META/ROOT regions
--------------------------------------------------------------------------

                 Key: HBASE-4276
                 URL: https://issues.apache.org/jira/browse/HBASE-4276
             Project: HBase
          Issue Type: Improvement
          Components: master
    Affects Versions: 0.90.4
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon
            Priority: Minor
             Fix For: 0.90.5


The master debug logs are quite verbose, so people don't usually have them all on. But, when trying to debug why a cluster's in a bad state due to META or ROOT issues, it's really helpful to have this info. So, for any transition info for these important regions, we should always log details at INFO level.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-4276) AssignmentManager debug logs should be at INFO level for META/ROOT regions

Posted by "stack (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093411#comment-13093411 ] 

stack commented on HBASE-4276:
------------------------------

+1

> AssignmentManager debug logs should be at INFO level for META/ROOT regions
> --------------------------------------------------------------------------
>
>                 Key: HBASE-4276
>                 URL: https://issues.apache.org/jira/browse/HBASE-4276
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.90.4
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 0.90.5
>
>         Attachments: 0011-HBASE-4276.-INFO-level-logging-for-transitions-of-me.patch
>
>
> The master debug logs are quite verbose, so people don't usually have them all on. But, when trying to debug why a cluster's in a bad state due to META or ROOT issues, it's really helpful to have this info. So, for any transition info for these important regions, we should always log details at INFO level.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (HBASE-4276) AssignmentManager debug logs should be at INFO level for META/ROOT regions

Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon resolved HBASE-4276.
--------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

Committed to trunk with the fix as described above

> AssignmentManager debug logs should be at INFO level for META/ROOT regions
> --------------------------------------------------------------------------
>
>                 Key: HBASE-4276
>                 URL: https://issues.apache.org/jira/browse/HBASE-4276
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.90.4
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 0.90.5
>
>         Attachments: 0011-HBASE-4276.-INFO-level-logging-for-transitions-of-me.patch, hbase-4276-v2.txt
>
>
> The master debug logs are quite verbose, so people don't usually have them all on. But, when trying to debug why a cluster's in a bad state due to META or ROOT issues, it's really helpful to have this info. So, for any transition info for these important regions, we should always log details at INFO level.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HBASE-4276) AssignmentManager debug logs should be at INFO level for META/ROOT regions

Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated HBASE-4276:
-------------------------------

    Attachment: 0011-HBASE-4276.-INFO-level-logging-for-transitions-of-me.patch

> AssignmentManager debug logs should be at INFO level for META/ROOT regions
> --------------------------------------------------------------------------
>
>                 Key: HBASE-4276
>                 URL: https://issues.apache.org/jira/browse/HBASE-4276
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.90.4
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 0.90.5
>
>         Attachments: 0011-HBASE-4276.-INFO-level-logging-for-transitions-of-me.patch
>
>
> The master debug logs are quite verbose, so people don't usually have them all on. But, when trying to debug why a cluster's in a bad state due to META or ROOT issues, it's really helpful to have this info. So, for any transition info for these important regions, we should always log details at INFO level.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HBASE-4276) AssignmentManager debug logs should be at INFO level for META/ROOT regions

Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated HBASE-4276:
-------------------------------

    Attachment: hbase-4276-v2.txt

I committed this, then realized I made the mistake of only checking for isMetaRegion, and didn't do the same for ROOT. I reverted the commit. Here's an improved patch.

> AssignmentManager debug logs should be at INFO level for META/ROOT regions
> --------------------------------------------------------------------------
>
>                 Key: HBASE-4276
>                 URL: https://issues.apache.org/jira/browse/HBASE-4276
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.90.4
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 0.90.5
>
>         Attachments: 0011-HBASE-4276.-INFO-level-logging-for-transitions-of-me.patch, hbase-4276-v2.txt
>
>
> The master debug logs are quite verbose, so people don't usually have them all on. But, when trying to debug why a cluster's in a bad state due to META or ROOT issues, it's really helpful to have this info. So, for any transition info for these important regions, we should always log details at INFO level.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-4276) AssignmentManager debug logs should be at INFO level for META/ROOT regions

Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094132#comment-13094132 ] 

Todd Lipcon commented on HBASE-4276:
------------------------------------

Also committed to branch.

> AssignmentManager debug logs should be at INFO level for META/ROOT regions
> --------------------------------------------------------------------------
>
>                 Key: HBASE-4276
>                 URL: https://issues.apache.org/jira/browse/HBASE-4276
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.90.4
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 0.90.5
>
>         Attachments: 0011-HBASE-4276.-INFO-level-logging-for-transitions-of-me.patch, hbase-4276-v2.txt
>
>
> The master debug logs are quite verbose, so people don't usually have them all on. But, when trying to debug why a cluster's in a bad state due to META or ROOT issues, it's really helpful to have this info. So, for any transition info for these important regions, we should always log details at INFO level.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-4276) AssignmentManager debug logs should be at INFO level for META/ROOT regions

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094189#comment-13094189 ] 

Hudson commented on HBASE-4276:
-------------------------------

Integrated in HBase-TRUNK #2163 (See [https://builds.apache.org/job/HBase-TRUNK/2163/])
    HBASE-4276  AssignmentManager debug logs should be at INFO level for META/ROOT regions.
Revert previous commit of HBASE-4276

Realized after committing that the conditions should check
isMetaTable || isRootRegion, not just isMetaTable. Will recommit
a fixed version.
Previous commit purported to revert HBASE-4276, but accidentally reverted HBASE-4293.

This commit re-applies HBASE-4293. The next commit will _actually_ revert HBASE-4276
Revert previous commit of HBASE-4276

Realized after committing that the conditions should check
isMetaTable || isRootRegion, not just isMetaTable. Will recommit
a fixed version.
HBASE-4276  AssignmentManager debug logs should be at INFO level for META/ROOT regions.

todd : 
Files : 
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/OpenedRegionHandler.java

todd : 
Files : 
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/OpenedRegionHandler.java

todd : 
Files : 
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java

todd : 
Files : 
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java

todd : 
Files : 
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/OpenedRegionHandler.java


> AssignmentManager debug logs should be at INFO level for META/ROOT regions
> --------------------------------------------------------------------------
>
>                 Key: HBASE-4276
>                 URL: https://issues.apache.org/jira/browse/HBASE-4276
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.90.4
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 0.90.5
>
>         Attachments: 0011-HBASE-4276.-INFO-level-logging-for-transitions-of-me.patch, hbase-4276-v2.txt
>
>
> The master debug logs are quite verbose, so people don't usually have them all on. But, when trying to debug why a cluster's in a bad state due to META or ROOT issues, it's really helpful to have this info. So, for any transition info for these important regions, we should always log details at INFO level.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira