[
https://issues.apache.org/jira/browse/STORM-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980736#comment-15980736
]
Arun Mahadevan commented on STORM-2489:
---------------------------------------
[~wangkui] thanks for reporting the issue. Processing-time based windows
internally uses a ScheduledExecutor. It maybe that the tasks are not triggered
exactly after the tumbling window interval causing some overlap. To debug
further, can you also print the window end timestamp
(https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/windowing/Window.java#L55)
each time the execute is invoked? "getEndTimestamp" returns the reference
processing time which is used to calculate the window boundaries.
You will need build storm from the latest master and run your examples against
that since "getEndTimestamp" is not available in any of the released versions
of storm.
> Overlap and data loss on WindowedBolt based on Duration
> -------------------------------------------------------
>
> Key: STORM-2489
> URL: https://issues.apache.org/jira/browse/STORM-2489
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 1.0.2
> Environment: windows 10, eclipse, jdk1.7
> Reporter: wangkui
> Attachments: TumblingWindowIssue.java
>
>
> The attachment is my test script, one of my test results is:
> ```
> expired=1...55
> get=56...4024
> new=56...4024
> Recived=3969,RecivedTotal=3969
> expired=56...4020
> get=4021...8191
> new=4025...8191
> Recived=4171,RecivedTotal=8140
> SendTotal=12175
> expired=4021...8188
> get=8189...12175
> new=8192...12175
> Recived=3987,RecivedTotal=12127
> ```
> This test result shows that some tuples appear in the expired list directly,
> we lost these data if we just use get() to get tuples, this is the first bug.
> The second: the tuples of get() has overlap, the getNew() seems alright.
> The problem not happen definitely, may need to try several times.
> Actually, I'm newbie about storm, so I'm not sure this is a bug indeed, or, I
> use it in wrong way?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
