[
https://issues.apache.org/jira/browse/STORM-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986049#comment-15986049
]
wangkui commented on STORM-2489:
--------------------------------
[~arunmahadevan] I test again, as the same arguments as before, it seems all
right. But when I make the spout emit more frequently, the ahead tuples are
expired, following test I spout data with out sleep() and use Duration(4sec)
window bolt,
Timestamp_start-end=1493271145887-1493271149887
expired=1...291972
get=291973...1189440
new=291973...1189440
Recived=897468,RecivedTotal=897468
13:32:34.470 [pool-45-thread-1] WARN o.a.s.w.TimeEvictionPolicy - Possible
clock drift or long running computation in window; Previous eviction time:
1493271149887, current eviction time: 1493271154469
Timestamp_start-end=1493271150469-1493271154469
expired=291973...1189440
get=1189441...2888803
new=1189441...2888803
Recived=1699363,RecivedTotal=2596831
13:32:39.213 [pool-45-thread-1] WARN o.a.s.w.TimeEvictionPolicy - Possible
clock drift or long running computation in window; Previous eviction time:
1493271154469, current eviction time: 1493271159212
SendTotal=5435440
Timestamp_start-end=1493271155212-1493271159212
expired=1189441...2888803
get=2888804...5069647
new=2888804...5069647
Recived=2180844,RecivedTotal=4777675
13:32:42.311 [pool-45-thread-1] WARN o.a.s.w.TimeEvictionPolicy - Possible
clock drift or long running computation in window; Previous eviction time:
1493271159212, current eviction time: 1493271162310
Timestamp_start-end=1493271158310-1493271162310
expired=2888804...5069647
get=5069648...5435440
new=5069648...5435440
Recived=365793,RecivedTotal=5143468
13:32:45.195 [pool-45-thread-1] WARN o.a.s.w.TimeEvictionPolicy - Possible
clock drift or long running computation in window; Previous eviction time:
1493271162310, current eviction time: 1493271165194
> 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
> Assignee: Arun Mahadevan
> Attachments: TumblingWindowIssue.java
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> 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)
