[
https://issues.apache.org/jira/browse/STORM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193812#comment-14193812
]
Jungtaek Lim edited comment on STORM-350 at 11/2/14 12:31 PM:
--------------------------------------------------------------
Yes, I've also looked source code but nothing is suspicious.
(though I think we're better to having timeout wait strategy and do nothing
with TimeoutException.)
So if some others reproduces message loss by your scenario, we may change LMAX
Disruptor version to upper or lower and see it may helps.
(and I've installed 0.9.3-rc1 with three machines, distributed, and ready to
run 'storm-perf-test' modified to compatible with 0.9.3-rc1.)
was (Author: kabhwan):
Yes, I've also looked source code but nothing is suspicious.
(though I think we're better to having timeout wait strategy and do nothing
with TimeoutException.)
So if some others reproduces message loss by your scenario, we may change LMAX
Disruptor version to upper or lower and see it may helps.
> Update disruptor to latest version (3.2.1)
> ------------------------------------------
>
> Key: STORM-350
> URL: https://issues.apache.org/jira/browse/STORM-350
> Project: Apache Storm
> Issue Type: Dependency upgrade
> Reporter: Boris Aksenov
> Assignee: Boris Aksenov
> Fix For: 0.9.3
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
