hi Misha, you are correct shell actions run in a random node of the cluster. there is no way to control that today. eventually we could add support for locality affinity leveraging yarn.
ssh action run in the specified host, bode cluster or not thx Alejandro (phone typing) On Nov 22, 2013, at 8:30, Misha Zhurkin <[email protected]> wrote: > Dear all -- > > despite RTFM-ing, it's still not absolutely clear to me -- is there _any_ > way to restrict a shell action to run on a specific node? > > It appears that JobTracker and NameNode are the only relevant config > parameters available to a shell action -- so the play here would be to > stand up a one-node cluster on that node if it is imperative to run jobs on > that specific instance, right?.. > > However, if using ssh action it appears that it is possible to dispatch it > to a specific host precisely using USER@HOST directive in the <host/> > parameter of the ssh action… > > Does this about sum it up? > > Cheers, and thanks!
