You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Pavel Smirnov (JIRA)" <ji...@apache.org> on 2016/05/11 16:52:12 UTC
[jira] [Updated] (STORM-1779) Incorrect bfs-ordering in
DefaultResourceAwareStrategy
[ https://issues.apache.org/jira/browse/STORM-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Smirnov updated STORM-1779:
---------------------------------
Description:
I have designed a simple diamond topology: spout, N parallel processingBolts, joinBolt.
https://github.com/smirnp/storm-benchmark/blob/1.0.0/src/storm/benchmark/DiamondTopology.java
For 6-component's topopoly the breadth-first search (bfs method in DefaultResourceAwareStrategy.java:323) returns 13 components, which is obviously incorrect for further scheduling (it tries to schedule already scheduled tasks in priorityToExecutorMap because of incorrect its length).
I have reimplemented bfs with the comparison with the original-one (https://github.com/smirnp/storm-benchmark/blob/1.0.0/bfs.txt)
Please check it and fix the bug in next releases.
P.S. storm.yaml user for scheduling is here:
https://github.com/smirnp/storm-benchmark/blob/1.0.0/storm.yaml
Best regards,
Thanks
was:
I have designed simple diamond topology:
spout, N parallel processingBolts, joinBolt.
(https://github.com/smirnp/storm-benchmark/blob/1.0.0/src/storm/benchmark/DiamondTopology.java)
For 6-component's topopoly the breadth-first search (bfs method in DefaultResourceAwareStrategy.java:323) returns 13 components, which is obviously incorrect for further scheduling.
I have reimplemented bfs with the comparison with the original-one (https://github.com/smirnp/storm-benchmark/blob/1.0.0/bfs.txt)
Please check it and fix a bug in next releases.
P.S. storm.yaml user for scheduling is here:
https://github.com/smirnp/storm-benchmark/blob/1.0.0/storm.yaml
Best regards,
Thanks
> Incorrect bfs-ordering in DefaultResourceAwareStrategy
> ------------------------------------------------------
>
> Key: STORM-1779
> URL: https://issues.apache.org/jira/browse/STORM-1779
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 1.0.0
> Reporter: Pavel Smirnov
> Priority: Minor
> Labels: bug, scheduler
>
> I have designed a simple diamond topology: spout, N parallel processingBolts, joinBolt.
> https://github.com/smirnp/storm-benchmark/blob/1.0.0/src/storm/benchmark/DiamondTopology.java
> For 6-component's topopoly the breadth-first search (bfs method in DefaultResourceAwareStrategy.java:323) returns 13 components, which is obviously incorrect for further scheduling (it tries to schedule already scheduled tasks in priorityToExecutorMap because of incorrect its length).
> I have reimplemented bfs with the comparison with the original-one (https://github.com/smirnp/storm-benchmark/blob/1.0.0/bfs.txt)
> Please check it and fix the bug in next releases.
> P.S. storm.yaml user for scheduling is here:
> https://github.com/smirnp/storm-benchmark/blob/1.0.0/storm.yaml
> Best regards,
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)