You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2012/09/18 23:52:09 UTC

[jira] [Created] (MAPREDUCE-4666) JVM metrics for history server

Jason Lowe created MAPREDUCE-4666:
-------------------------------------

             Summary: JVM metrics for history server
                 Key: MAPREDUCE-4666
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
          Components: jobhistoryserver
    Affects Versions: 2.0.2-alpha
            Reporter: Jason Lowe
            Priority: Minor


It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
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] (MAPREDUCE-4666) JVM metrics for history server

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

Hudson commented on MAPREDUCE-4666:
-----------------------------------

Integrated in Hadoop-Hdfs-0.23-Build #431 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/431/])
    MAPREDUCE-4666. JVM metrics for history server. (jlowe via jeagles) (Revision 1407671)

     Result = UNSTABLE
jeagles : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1407671
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/JobHistoryServer.java

                
> JVM metrics for history server
> ------------------------------
>
>                 Key: MAPREDUCE-4666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Minor
>             Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
>         Attachments: MAPREDUCE-4666.patch
>
>
> It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
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] (MAPREDUCE-4666) JVM metrics for history server

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

Hudson commented on MAPREDUCE-4666:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #1253 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1253/])
    MAPREDUCE-4666. JVM metrics for history server. (jlowe via jeagles) (Revision 1407669)

     Result = FAILURE
jeagles : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1407669
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/JobHistoryServer.java

                
> JVM metrics for history server
> ------------------------------
>
>                 Key: MAPREDUCE-4666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Minor
>             Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
>         Attachments: MAPREDUCE-4666.patch
>
>
> It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
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] (MAPREDUCE-4666) JVM metrics for history server

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

Hudson commented on MAPREDUCE-4666:
-----------------------------------

Integrated in Hadoop-Yarn-trunk #32 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/32/])
    MAPREDUCE-4666. JVM metrics for history server. (jlowe via jeagles) (Revision 1407669)

     Result = SUCCESS
jeagles : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1407669
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/JobHistoryServer.java

                
> JVM metrics for history server
> ------------------------------
>
>                 Key: MAPREDUCE-4666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Minor
>             Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
>         Attachments: MAPREDUCE-4666.patch
>
>
> It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
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] (MAPREDUCE-4666) JVM metrics for history server

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

Jason Lowe updated MAPREDUCE-4666:
----------------------------------

    Attachment: MAPREDUCE-4666.patch

Patch to add metrics2 JvmMetrics to the history server.  I manually tested this to verify the metrics could be used via a sink configured in hadoop-metrics2.properties.  I also verified the JvmMetrics bean shows up via the JMX web service.
                
> JVM metrics for history server
> ------------------------------
>
>                 Key: MAPREDUCE-4666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Priority: Minor
>         Attachments: MAPREDUCE-4666.patch
>
>
> It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
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] (MAPREDUCE-4666) JVM metrics for history server

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

Jonathan Eagles updated MAPREDUCE-4666:
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.23.5
                   2.0.3-alpha
                   3.0.0
           Status: Resolved  (was: Patch Available)
    
> JVM metrics for history server
> ------------------------------
>
>                 Key: MAPREDUCE-4666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Minor
>             Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
>         Attachments: MAPREDUCE-4666.patch
>
>
> It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
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] (MAPREDUCE-4666) JVM metrics for history server

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493579#comment-13493579 ] 

Hadoop QA commented on MAPREDUCE-4666:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12552712/MAPREDUCE-4666.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 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any 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:green}+1 core tests{color}.  The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3001//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3001//console

This message is automatically generated.
                
> JVM metrics for history server
> ------------------------------
>
>                 Key: MAPREDUCE-4666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Minor
>         Attachments: MAPREDUCE-4666.patch
>
>
> It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
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] (MAPREDUCE-4666) JVM metrics for history server

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

Hudson commented on MAPREDUCE-4666:
-----------------------------------

Integrated in Hadoop-trunk-Commit #2996 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/2996/])
    MAPREDUCE-4666. JVM metrics for history server. (jlowe via jeagles) (Revision 1407669)

     Result = SUCCESS
jeagles : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1407669
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/JobHistoryServer.java

                
> JVM metrics for history server
> ------------------------------
>
>                 Key: MAPREDUCE-4666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Minor
>             Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
>         Attachments: MAPREDUCE-4666.patch
>
>
> It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
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] (MAPREDUCE-4666) JVM metrics for history server

Posted by "Jonathan Eagles (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494353#comment-13494353 ] 

Jonathan Eagles commented on MAPREDUCE-4666:
--------------------------------------------

+1. simple change that works for me.
                
> JVM metrics for history server
> ------------------------------
>
>                 Key: MAPREDUCE-4666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Minor
>         Attachments: MAPREDUCE-4666.patch
>
>
> It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
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] (MAPREDUCE-4666) JVM metrics for history server

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

Jason Lowe updated MAPREDUCE-4666:
----------------------------------

            Assignee: Jason Lowe
    Target Version/s: 2.0.3-alpha, 0.23.5
              Status: Patch Available  (was: Open)
    
> JVM metrics for history server
> ------------------------------
>
>                 Key: MAPREDUCE-4666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Minor
>         Attachments: MAPREDUCE-4666.patch
>
>
> It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
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] (MAPREDUCE-4666) JVM metrics for history server

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

Hudson commented on MAPREDUCE-4666:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk #1222 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1222/])
    MAPREDUCE-4666. JVM metrics for history server. (jlowe via jeagles) (Revision 1407669)

     Result = SUCCESS
jeagles : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1407669
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/JobHistoryServer.java

                
> JVM metrics for history server
> ------------------------------
>
>                 Key: MAPREDUCE-4666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Minor
>             Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
>         Attachments: MAPREDUCE-4666.patch
>
>
> It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
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