Thanks Harsh, I got it.
On Sat, Feb 8, 2014 at 7:33 PM, Harsh J <ha...@cloudera.com> wrote: > Correction: Set it to 1 (For 1 max attempt), not 0. > > On Sat, Feb 8, 2014 at 7:31 PM, Harsh J <ha...@cloudera.com> wrote: > > You can set > http://hadoop.apache.org/docs/current/api/org/apache/hadoop/yarn/api/records/ApplicationSubmissionContext.html#setMaxAppAttempts(int) > > to 0, at a per-app level, to prevent any reattempts/recovery of your > > AM. > > > > For a cluster-wide effect instead, you can limit by overriding the > > default value of the RM property yarn.resourcemanager.am.max-retries > > in the RM's YarnConfiguration or yarn-site.xml. > > > > On Fri, Feb 7, 2014 at 5:24 PM, Krishna Kishore Bonagiri > > <write2kish...@gmail.com> wrote: > >> Hi, > >> > >> I am having some failure test cases where my Application Master is > >> supposed to fail. But when it fails it is again started with <appID>_02 > . Is > >> there a way for me to avoid the second instance of the Application > Master > >> getting started? Is it re-started automatically by the RM after the > first > >> one failed? > >> > >> Thanks, > >> Kishore > > > > > > > > -- > > Harsh J > > > > -- > Harsh J >
