[
https://issues.apache.org/jira/browse/STORM-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968116#comment-14968116
]
ASF GitHub Bot commented on STORM-1121:
---------------------------------------
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/810#issuecomment-150047429
I also love the concept.
Btw, in order to rely on recurring mk-assignments,
- We should remove ```nimbus.reassign``` since it should be true for new
topologies to be assigned. We can't change ```when statement``` cause it makes
nimbus.reassign ineffective.
- It would be better to let users know that new topology will be assigned
by nimbus not at the moment but within ```nimbus.monitor.freq.secs```.
```
(schedule-recurring (:timer nimbus)
0
(conf NIMBUS-MONITOR-FREQ-SECS)
(fn []
(when (conf NIMBUS-REASSIGN)
(locking (:submit-lock nimbus)
(mk-assignments nimbus)))
(do-cleanup nimbus)
))
```
> Improve Nimbus Topology submission time
> ---------------------------------------
>
> Key: STORM-1121
> URL: https://issues.apache.org/jira/browse/STORM-1121
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Kishor Patil
> Assignee: Kishor Patil
>
> It appears, nimbus is blocking itself as active topologies count goes up. It
> increases submitTopology response time exponentially for submission of newer
> topology.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
