[
https://issues.apache.org/jira/browse/OOZIE-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598945#comment-17598945
]
Janos Makai commented on OOZIE-3666:
------------------------------------
Hello,
did you get a chance to check my recent patch?
Thanks in advance. :)
cc [~dionusos] [~asalamon74]
> Oozie log streaming bug when log timestamps are the same on multiple Oozie
> servers
> ----------------------------------------------------------------------------------
>
> Key: OOZIE-3666
> URL: https://issues.apache.org/jira/browse/OOZIE-3666
> Project: Oozie
> Issue Type: Bug
> Components: core
> Reporter: Janos Makai
> Assignee: Janos Makai
> Priority: Major
> Labels: usability
> Attachments: OOZIE-3666-001.patch, OOZIE-3666-002.patch,
> OOZIE-3666-003.patch
>
>
> We have found a bug in the mechanism of the Oozie log streaming.
> Affected code lines:
> [https://github.com/apache/oozie/blob/release-5.2.1/core/src/main/java/org/apache/oozie/service/ZKXLogStreamingService.java#L221L250]
> This code is responsible for collating all of the logs from the available
> Oozie servers.However, in case there is a log message in server "A" with the
> same timestamp as an other log message in server "B", then according to the
> current implementation, the logs acquired by using `TimestampedMessageParser`
> corresponding to server "B" will be overwritten by server "A" 's parser (due
> to the operation of
> {*}{color:#0747a6}timestampMap.put(earliestParser.getLastTimestamp(),
> earliestParser){color}{*}), therefore causing the log messages from server
> "B" to be ignored from that point.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
