Hi, @Petr. > Like if I want to run my task collocated with some other tasks on the same node I have to make this decision somewhere. Do you mean "POD" here?
For my cases, if there are some dependencies between my tasks, I use database, message queue or zookeeper to implement my requirement. On Wed, Dec 14, 2016 at 3:09 AM, Petr Novak <[email protected]> wrote: > Hello, > > I want to execute tasks which requires some other tasks from other > framework(s) already running. I’m thinking where such logic/strategy/policy > belongs in principle. I understand scheduling as a process to decide where > to execute task according to some resources availability, typically CPU, > mem, net, hdd etc. > > > > If my task require other tasks running could I generalize and consider > that those tasks from other frameworks are kind of required resources and > put this logic/strategy decisions into scheduler? Like if I want to run my > task collocated with some other tasks on the same node I have to make this > decision somewhere. > > > > Does it make any sense? I’m asking because I have never thought about > other frameworks/tasks as “resources” so that I could put them into > scheduler to satisfy my understanding of a scheduler. Or it rather belongs > higher like to a framework, or lower to an executor? Should scheduler be > dedicated to decisions about resources which are offered and am I mixing > concepts? > > > > Or I just should keep distinction between resources and > requirements/policies or whatever but anyway does this kind of logic still > belongs to scheduler or it should be somewhere else? I’m trying to > understand which logic should be in scheduler and what should go somewhere > else. > > > > Many thanks, > > Petr > > > -- Best Regards, Haosdent Huang
