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/11/13 02:52:12 UTC
[jira] [Created] (GIRAPH-422) Setting the log level of the root
logger to the same level can cause issues in Hadoop
Avery Ching created GIRAPH-422:
----------------------------------
Summary: Setting the log level of the root logger to the same level can cause issues in Hadoop
Key: GIRAPH-422
URL: https://issues.apache.org/jira/browse/GIRAPH-422
Project: Giraph
Issue Type: Bug
Reporter: Avery Ching
Assignee: Avery Ching
Attachments: GIRAPH-422.patch
For some reason, setting the log level to the same level causes syslog to not be populated. A quick fix is to not set the log level if the current level is the same.
--
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-422) Setting the log level of the root
logger to the same level can cause issues in Hadoop
Posted by "Alessandro Presta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495857#comment-13495857 ]
Alessandro Presta commented on GIRAPH-422:
------------------------------------------
+1, thanks for the quick fix!
> Setting the log level of the root logger to the same level can cause issues in Hadoop
> -------------------------------------------------------------------------------------
>
> Key: GIRAPH-422
> URL: https://issues.apache.org/jira/browse/GIRAPH-422
> Project: Giraph
> Issue Type: Bug
> Reporter: Avery Ching
> Assignee: Avery Ching
> Attachments: GIRAPH-422.2.patch, GIRAPH-422.patch
>
>
> For some reason, setting the log level to the same level causes syslog to not be populated. A quick fix is to not set the log level if the current level is the same.
--
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-422) Setting the log level of the root
logger to the same level can cause issues in Hadoop
Posted by "Avery Ching (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Avery Ching updated GIRAPH-422:
-------------------------------
Attachment: GIRAPH-422.patch
> Setting the log level of the root logger to the same level can cause issues in Hadoop
> -------------------------------------------------------------------------------------
>
> Key: GIRAPH-422
> URL: https://issues.apache.org/jira/browse/GIRAPH-422
> Project: Giraph
> Issue Type: Bug
> Reporter: Avery Ching
> Assignee: Avery Ching
> Attachments: GIRAPH-422.patch
>
>
> For some reason, setting the log level to the same level causes syslog to not be populated. A quick fix is to not set the log level if the current level is the same.
--
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-422) Setting the log level of the root
logger to the same level can cause issues in Hadoop
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495910#comment-13495910 ]
Hudson commented on GIRAPH-422:
-------------------------------
Integrated in Giraph-trunk-Commit #280 (See [https://builds.apache.org/job/Giraph-trunk-Commit/280/])
GIRAPH-422: Setting the log level of the root logger to the same level
can cause issues in Hadoop. (aching) (Revision 1408538)
Result = SUCCESS
aching : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1408538
Files :
* /giraph/trunk/CHANGELOG
* /giraph/trunk/giraph/src/main/java/org/apache/giraph/graph/GraphMapper.java
> Setting the log level of the root logger to the same level can cause issues in Hadoop
> -------------------------------------------------------------------------------------
>
> Key: GIRAPH-422
> URL: https://issues.apache.org/jira/browse/GIRAPH-422
> Project: Giraph
> Issue Type: Bug
> Reporter: Avery Ching
> Assignee: Avery Ching
> Attachments: GIRAPH-422.2.patch, GIRAPH-422.patch
>
>
> For some reason, setting the log level to the same level causes syslog to not be populated. A quick fix is to not set the log level if the current level is the same.
--
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-422) Setting the log level of the root
logger to the same level can cause issues in Hadoop
Posted by "Avery Ching (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Avery Ching updated GIRAPH-422:
-------------------------------
Attachment: GIRAPH-422.2.patch
Missing a log wrapper. Passed 'mvn clean install' and also the syslog is shown when using the default level.
> Setting the log level of the root logger to the same level can cause issues in Hadoop
> -------------------------------------------------------------------------------------
>
> Key: GIRAPH-422
> URL: https://issues.apache.org/jira/browse/GIRAPH-422
> Project: Giraph
> Issue Type: Bug
> Reporter: Avery Ching
> Assignee: Avery Ching
> Attachments: GIRAPH-422.2.patch, GIRAPH-422.patch
>
>
> For some reason, setting the log level to the same level causes syslog to not be populated. A quick fix is to not set the log level if the current level is the same.
--
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