Yarn kill cli was added with https://issues.apache.org/jira/browse/YARN-40. It will be in the 2.0.3 release.
Tom On 11/26/12 2:39 AM, "Matthieu Morel" <[email protected]> wrote: >Thanks for your answer Chris, > >however this does not work on yarn 2.0.2-alpha : there is no "bin/yarn >application " command available with the yarn distribution built through >the "dist" command (only, bin/yarn [resourcemanager | nodemager | rmadmin >| version | jar | logs | class path | daemonlog | CLASSNAME] ) > >Is this command available for a specific version only? > >If I find it then I should be able to infer how to do that >programmatically as well. > >Thanks, > >Matthieu > > > > >On Nov 23, 2012, at 5:54 PM, Chris Nauroth wrote: > >> The yarn CLI script provides kill as a sub-command of the application >> command: >> >> bin/yarn application -kill <application_id> >> >> Is this what you need? >> >> --Chris >> >> On Thu, Nov 22, 2012 at 6:07 AM, Matthieu Morel >><[email protected]>wrote: >> >>> Hello, >>> >>> I am working with yarn 2.0.2-alpha. >>> >>> >>> I want to be able to properly terminate long running applications >>>deployed >>> on Yarn. However, I can't see any tool to do that from the command line >>> (something like "hadoop job -kill #jobid". but for yarn). It's not >>>clear to >>> me how to do that programmatically either. >>> >>> Is this left to the developer of the application master? Is there a >>> recommended way? >>> >>> >>> Currently an option I see is to implement a callback from some >>> notification in the application master (e.g. a signal from ZooKeeper), >>> terminate the launched container properly, through the >>> ContainerManager#stopContainer method. But there might be a more >>>generic >>> way? >>> >>> I also noted that ClientRMProtocol#forceKillApplication does not >>>properly >>> kill spawned processes, apart from the application master, at least >>>when >>> using MiniYarnCluster in tests. >>> >>> >>> Thanks for any suggestion or recommendation ! >>> >>> >>> Matthieu >>> >>> >
