You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Satish Subhashrao Saley (JIRA)" <ji...@apache.org> on 2017/05/01 22:55:04 UTC

[jira] [Comment Edited] (OOZIE-2815) Oozie not always display job log

    [ https://issues.apache.org/jira/browse/OOZIE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991335#comment-15991335 ] 

Satish Subhashrao Saley edited comment on OOZIE-2815 at 5/1/17 10:54 PM:
-------------------------------------------------------------------------

Reopening for amend patch to fix flaky test failures

Following tests were failing because Services singleton was null. It depends on the sequence of tests run, so sometimes we see success while running these tests with other tests. Fixing it by initializing Services.
org.apache.oozie.util.TestTimestampedMessageParser.testNofindLogs 5 ms 3
org.apache.oozie.util.TestTimestampedMessageParser.testProcessRemainingLog 0 ms 3
org.apache.oozie.util.TestTimestampedMessageParser.testProcessRemainingCoordinatorLogForActions


was (Author: satishsaley):
Reopening for amend patch to fix flaky test failures

> Oozie not always display job log
> --------------------------------
>
>                 Key: OOZIE-2815
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2815
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Purshotam Shah
>            Assignee: Satish Subhashrao Saley
>             Fix For: 5.0.0
>
>         Attachments: OOZIE-2815-amend-1.patch, OOZIE-2815-V2.patch, OOZIE-2815-V3.patch, OOZIE-2815-V4.patch, OOZIE-2815-V5.patch
>
>
> There are few issues with log streaming. We will fix following things.
> 1. UI has an issue with displaying "loading... done". It used to show loading done even if logs were not loaded entirely.
> 2. Server-server communication time out. The default time is 1 min. Setting to 3 min same as UI.
> 3. We use to throw an error message if log scan duration is more than configured duration. We will be truncating log.
> 4. No log scan duration check for audit and error log since it doesn't support log filter.
> 5. Different buffer.len setting for error and audit log, so that partial loading can be faster. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)