GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/2257
STORM-2673: add support for prioritizing nodes in scheduling
I really would like feedback on the configs and if it makes since to modify
other schedulers to support this too.
Config:
I thought about using regexs for nodes instead of just a host name. Would
that be better? Would it make it simple for someone to prefer a large section
of a cluster and essentially abuse the feature?
Other Schedulers:
The isolation scheduler possibly, where we could resort The
HostAssignableSlots if the topology want to prioritize one host over another.
And then sort them back if they don't
The even scheduler is a little odd as it feels completely against what it
stands for. It would almost turn it into an odd hybrid with the isolation
scheduler.
MT scheduler is so complex at this point I could do it, but only if someone
really wants it.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm STORM-2673
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/2257.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2257
----
commit 9b4c30dab0bc2828c4675d94a1e834a092ae8635
Author: Robert (Bobby) Evans <ev...@yahoo-inc.com>
Date: 2017-08-02T19:21:11Z
STORM-2673: add support for prioritizing nodes in scheduling
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
