You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gearpump.apache.org by "Manu Zhang (JIRA)" <ji...@apache.org> on 2017/06/19 03:48:02 UTC
[jira] [Resolved] (GEARPUMP-317) Task minClock could be non
increasing
[ https://issues.apache.org/jira/browse/GEARPUMP-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manu Zhang resolved GEARPUMP-317.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.8.4
Issue resolved by pull request 187
[https://github.com/apache/incubator-gearpump/pull/187]
> Task minClock could be non increasing
> -------------------------------------
>
> Key: GEARPUMP-317
> URL: https://issues.apache.org/jira/browse/GEARPUMP-317
> Project: Apache Gearpump
> Issue Type: Bug
> Components: streaming
> Affects Versions: 0.8.3
> Reporter: Manu Zhang
> Assignee: Manu Zhang
> Fix For: 0.8.4
>
>
> Task minClock is the minimum of upstream minClock and output minClock. Considering the following scenario,
> 1. Output minClock is set to Long.MaxValue since all messages have been acked by downstream tasks
> 2. But there are messages buffered in a window function
> 3. Later the window is triggered and those messages are emitted, which will set the output minClock to a smaller value.
> 4. Plus, the output messages are possibly not in time order, which again will make output minClock non increasing.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)