[
https://issues.apache.org/jira/browse/STORM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904506#comment-14904506
]
ASF GitHub Bot commented on STORM-350:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/750#issuecomment-142601291
@HeartSaVioR I figured out the failed tuples and will be pushing a new
patch shortly. This is the same null issue we were seeing previously. Just
with the newer disruptor it exacerbates the two issues.
First MutableObject is not synchronized so it is possible for the data to
not be flushed to memory and if the receiver thread is on a different core you
can get a null out.
Additionally I noticed that the non-bocking receive seems to not be putting
the correct barriers in place, and the polling can try to read a MutableObject
that has not been updated yet, and is still set to null. The only way I could
find to fix it was to implement it in terms of the blocking call. From my
performance tests I did not see any impact from these changes.
> 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: Improvement
> Reporter: Boris Aksenov
> Assignee: Boris Aksenov
> Priority: Minor
> Fix For: 0.10.0
>
> Attachments:
> 20141117-0.9.3-rc1-3-worker-separate-1-spout-and-2-bolts-failing-tuples.png,
> 20141117-0.9.3-rc1-one-worker-failing-tuples.png,
> 20141117-0.9.3-rc1-three-workers-1-spout-3-bolts-failing-tuples.png,
> 20141118-0.9.3-branch-3-worker-separate-1-spout-and-2-bolts-ok.png,
> 20141118-0.9.3-branch-one-worker-ok.png,
> 20141118-0.9.3-branch-three-workers-1-spout-3-bolts-ok.png, Storm UI1.pdf,
> Storm UI2.pdf, storm-0.9.3-rc1-failing-tuples.png,
> storm-0_9_2-incubating-failing-tuples.png,
> storm-0_9_2-incubating-no-failing-tuples.png,
> storm-failed-tuples-multi-node.png, storm-multi-node-without-350.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
