Hi Shekar, My guess is that, in order to get this property to take effect, you may need to restart the yarn. Otherwise, send this question to the Yarn mailing list, you may get more valuable answers.
Thanks, Fang, Yan yanfang...@gmail.com On Mon, Jun 22, 2015 at 2:43 PM, Shekar Tippur <ctip...@gmail.com> wrote: > Looks like when I kill an application ID, the next application ID in the > pending queue takes over. > As there are 2 running jobs, I see that for every in coming event, there > are 2 outputs. > a. How do I force to have just 1 running job > b. How to force the number of application pending to a smaller number? > > I looked at the document - > > https://hadoop.apache.org/docs/r2.4.1/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html > I have changed the property on capacity-scheduler.xml to a low number. I > still see 10k apps in pending state. > > > <property> > > <name>yarn.scheduler.capacity.maximum-applications</name> > > <value>2</value> > > <description> > > Maximum number of applications that can be pending and running. > > </description> > > </property> >
