I **guess** you could use the “tag-aware scheduling” described here: https://inside.edited.com/taking-control-of-your-apache-storm-cluster-with-tag-aware-scheduling-b60aaaa5e37e Or maybe bend the "resource aware scheduler" presented here: https://storm.apache.org/releases/2.0.0-SNAPSHOT/Resource_Aware_Scheduler_overview.html to do what you want, but that sounds hackish.
Anyways, I've never used any of them so I'm just sending the links for further reading. Hope this helps. On Thu, Feb 8, 2018, 12:12 AM Mitchell Rathbun (BLOOMBERG/ 731 LEX) < [email protected]> wrote: > Given a multiple node Storm cluster, is it possible to ensure that a > topology submitted on a specific machine runs only on that machine? More > specifically, given a cluster of machines A, B, and C, if a topology is > submitted from machine A, is there a way to guarantee that: > > -The topology runs on machine A. > -If machine A crashes, the topology is not re-run on another machine. > > I am guessing there isn't and that the answer to this is to run a leader > nimbus per machine (nimbus.seeds: ["localhost"]), but I wanted to see if > there was a way to do this that I am missing. >
