[
https://issues.apache.org/jira/browse/OOZIE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003664#comment-16003664
]
Peter Cseh commented on OOZIE-2815:
-----------------------------------
[~satishsaley], please make sure that the {{Services}} used for testing is
destroyed.
I'd suggest to use the pattern in
[ActionExecutorTestCase|https://github.com/apache/oozie/blob/master/core/src/test/java/org/apache/oozie/action/hadoop/ActionExecutorTestCase.java#L65-L85]
> 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)
