[
https://issues.apache.org/jira/browse/STORM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903611#comment-14903611
]
ASF GitHub Bot commented on STORM-350:
--------------------------------------
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/750#issuecomment-142443503
@revans2
I ran performance test from small cluster (three machines, each one has
zookeeper and supervisor, and only one has zookeeper, nimbus, supervisor) with
configuration below,
> com.yahoo.storm.perftest.Main --ack --bolt 4 --name test -l 1 -n 1
--workers 4 --spout 3 --testTimeSec 900 -c topology.max.spout.pending=1092
--messageSize 10
Unfortunately I'm seeing failed tuples again.
<img width="1264" alt="storm-ui-failed-tuple-appeared"
src="https://cloud.githubusercontent.com/assets/1317309/10033834/d29c01d0-61c6-11e5-8cfd-381c693b1978.png">
I packaged perf test with 0.10.0-rc of storm-core, but I think it doesn't
matter cause its scope is provided.
I still don't know why this happens. According to log files, there's no
Netty connection issue.
Could you test it too?
> 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)