[
https://issues.apache.org/jira/browse/OOZIE-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979352#comment-13979352
]
Hadoop QA commented on OOZIE-1737:
----------------------------------
Testing JIRA OOZIE-1737
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:red}-1{color} the patch contains 48 line(s) with tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:red}-1{color} the patch contains 31 line(s) longer than 132
characters
. {color:green}+1{color} the patch does adds/modifies 9 testcase(s)
{color:red}-1 RAT{color}
. {color:red}-1{color} the patch seems to introduce 1 new RAT warning(s)
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
. Tests run: 1437
. Tests failed: 6
. Tests errors: 1
. The patch failed the following testcases:
.
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)
. testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
.
testCoordDefinitionChangeError(org.apache.oozie.command.coord.TestCoordUpdateXCommand)
. testStreamLog(org.apache.oozie.util.TestLogStreamer)
. testStreamLogMultipleHours(org.apache.oozie.util.TestLogStreamer)
. testStreamLogNoDash(org.apache.oozie.util.TestLogStreamer)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1192/
> Oozie log streaming is slow
> ---------------------------
>
> Key: OOZIE-1737
> URL: https://issues.apache.org/jira/browse/OOZIE-1737
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
> Assignee: Purshotam Shah
> Attachments: OOZIE-1737-V5.patch, OOZIE-1737-V6.patch
>
>
> Most of cases, Oozie search huge set of log files and return lot of logs.
> Most of our users has complained that log streaming is slow and they can't
> easily find relevant information.
> To make log streaming fast and precise we should provide few options (which
> user can specify for log streaming) like
> 1. Start time : Start date (if number, then offset(in hour) from
> coord/wf/bundle start)
> 2. End time : End date (if number, then offset from coord/wf/bundle start)
> 3. Log level :
> Setting log level to ERROR, will only give erred log and exception.
> In most of cases user want to find out error message and exception.
> 4. Number of lines : limit number of lines of logs from start date.
> 5. Recent logs: In most of the case user is only interested in recent
> activity.
> Similar to https://issues.apache.org/jira/browse/OOZIE-1716.
> User should be able to specify recent logs in hours.
> 6. Grep for pattern.
> + in addition to this, we also need to clean up log statements( which may
> also include consolidating log statements).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
