[
https://issues.apache.org/jira/browse/OOZIE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439291#comment-13439291
]
Hadoop QA commented on OOZIE-918:
---------------------------------
Testing JIRA OOZIE-918
{code}
----------------------------
+1 PATCH_APPLIES
CLEAN cleaned target directories
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
-1 TESTS - the patch failed the following testcases:
org.apache.oozie.service.TestStatusTransitService
Tests run: 874
Tests failures: 1
Tests errors: 0
----------------------------
{code}
The full output of the test-patch run is available at
https://builds.apache.org/job/oozie-trunk-precommit-build/39/
> Changing log level from DEBUG to TRACE for trivial log statements
> -----------------------------------------------------------------
>
> Key: OOZIE-918
> URL: https://issues.apache.org/jira/browse/OOZIE-918
> Project: Oozie
> Issue Type: Task
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-918.patch, OOZIE-918v1.patch
>
>
> We encountered a case of log files bloating up for large jobs or stuck jobs.
> Oozie will execute a lot of XCommands and some trivial logging statements
> which only mark the position in code, are cluttering the logs when run in
> DEBUG. So reducing their level to TRACE
--
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
