You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Avery Ching (JIRA)" <ji...@apache.org> on 2012/09/06 20:43:07 UTC

[jira] [Created] (GIRAPH-320) Provide a runtime configuration for choosing the log level

Avery Ching created GIRAPH-320:
----------------------------------

             Summary: Provide a runtime configuration for choosing the log level
                 Key: GIRAPH-320
                 URL: https://issues.apache.org/jira/browse/GIRAPH-320
             Project: Giraph
          Issue Type: Improvement
            Reporter: Avery Ching


Currently there is no easy way to control the log level for debugging in Giraph without making a cluster-wide setting.  This diff allows us to choose the log level at runtime, which is really nice for debugging vs performance testing.

--
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] (GIRAPH-320) Provide a runtime configuration for choosing the log level

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

Avery Ching updated GIRAPH-320:
-------------------------------

    Attachment: GIRAPH-320.patch

Pretty straightforward diff with one debug message downgraded to trace for usability.
                
> Provide a runtime configuration for choosing the log level
> ----------------------------------------------------------
>
>                 Key: GIRAPH-320
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-320
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Avery Ching
>            Assignee: Avery Ching
>         Attachments: GIRAPH-320.patch
>
>
> Currently there is no easy way to control the log level for debugging in Giraph without making a cluster-wide setting.  This diff allows us to choose the log level at runtime, which is really nice for debugging vs performance testing.

--
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] (GIRAPH-320) Provide a runtime configuration for choosing the log level

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

Hudson commented on GIRAPH-320:
-------------------------------

Integrated in Giraph-trunk-Commit #191 (See [https://builds.apache.org/job/Giraph-trunk-Commit/191/])
    GIRAPH-320: Provide a runtime configuration for choosing the log level (aching via ereisman) (Revision 1382399)

     Result = SUCCESS
ereisman : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1382399
Files : 
* /giraph/trunk/CHANGELOG
* /giraph/trunk/src/main/java/org/apache/giraph/graph/BspService.java
* /giraph/trunk/src/main/java/org/apache/giraph/graph/GiraphJob.java
* /giraph/trunk/src/main/java/org/apache/giraph/graph/GraphMapper.java
* /giraph/trunk/src/main/java/org/apache/giraph/io/PseudoRandomVertexInputFormat.java

                
> Provide a runtime configuration for choosing the log level
> ----------------------------------------------------------
>
>                 Key: GIRAPH-320
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-320
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Avery Ching
>            Assignee: Avery Ching
>         Attachments: GIRAPH-320.patch
>
>
> Currently there is no easy way to control the log level for debugging in Giraph without making a cluster-wide setting.  This diff allows us to choose the log level at runtime, which is really nice for debugging vs performance testing.

--
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] (GIRAPH-320) Provide a runtime configuration for choosing the log level

Posted by "Eli Reisman (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GIRAPH-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451501#comment-13451501 ] 

Eli Reisman commented on GIRAPH-320:
------------------------------------

+1, committed. Great idea!
                
> Provide a runtime configuration for choosing the log level
> ----------------------------------------------------------
>
>                 Key: GIRAPH-320
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-320
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Avery Ching
>            Assignee: Avery Ching
>         Attachments: GIRAPH-320.patch
>
>
> Currently there is no easy way to control the log level for debugging in Giraph without making a cluster-wide setting.  This diff allows us to choose the log level at runtime, which is really nice for debugging vs performance testing.

--
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] (GIRAPH-320) Provide a runtime configuration for choosing the log level

Posted by "Eli Reisman (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GIRAPH-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451371#comment-13451371 ] 

Eli Reisman commented on GIRAPH-320:
------------------------------------

I can try to commit this tonight or tomorrow if my car dies somewhere with internet service ;)
                
> Provide a runtime configuration for choosing the log level
> ----------------------------------------------------------
>
>                 Key: GIRAPH-320
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-320
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Avery Ching
>            Assignee: Avery Ching
>         Attachments: GIRAPH-320.patch
>
>
> Currently there is no easy way to control the log level for debugging in Giraph without making a cluster-wide setting.  This diff allows us to choose the log level at runtime, which is really nice for debugging vs performance testing.

--
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] [Assigned] (GIRAPH-320) Provide a runtime configuration for choosing the log level

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

Avery Ching reassigned GIRAPH-320:
----------------------------------

    Assignee: Avery Ching
    
> Provide a runtime configuration for choosing the log level
> ----------------------------------------------------------
>
>                 Key: GIRAPH-320
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-320
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Avery Ching
>            Assignee: Avery Ching
>         Attachments: GIRAPH-320.patch
>
>
> Currently there is no easy way to control the log level for debugging in Giraph without making a cluster-wide setting.  This diff allows us to choose the log level at runtime, which is really nice for debugging vs performance testing.

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