gearpump-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEARPUMP-317) Task minClock could be non increasing
Date Fri, 16 Jun 2017 07:18:00 GMT

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

ASF GitHub Bot commented on GEARPUMP-317:
-----------------------------------------

Github user codecov-io commented on the issue:

    https://github.com/apache/incubator-gearpump/pull/187
  
    # [Codecov](https://codecov.io/gh/apache/incubator-gearpump/pull/187?src=pr&el=h1)
Report
    > Merging [#187](https://codecov.io/gh/apache/incubator-gearpump/pull/187?src=pr&el=desc)
into [master](https://codecov.io/gh/apache/incubator-gearpump/commit/24e1a4546260ca414ca84f8df055e57f4d963263?src=pr&el=desc)
will **decrease** coverage by `1.16%`.
    > The diff coverage is `76.42%`.
    
    
    
    ```diff
    @@            Coverage Diff             @@
    ##           master     #187      +/-   ##
    ==========================================
    - Coverage   71.64%   70.47%   -1.17%     
    ==========================================
      Files         189      189              
      Lines        6087     6107      +20     
      Branches      528      534       +6     
    ==========================================
    - Hits         4361     4304      -57     
    - Misses       1726     1803      +77
    ```
    



> 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
>
> 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)

Mime
View raw message