You're looking for the property "yarn.nm.liveness-monitor.expiry-interval-ms", whose default is 600000ms (10m). This is to be set on the ResourceManager(s)' yarn-site.xml.
(X-Ref: https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-common/yarn-default.xml#yarn.nm.liveness-monitor.expiry-interval-ms ) On Sun, Feb 14, 2016 at 4:18 AM Caesar Samsi <[email protected]> wrote: > Hello, > > From testing it appears detecting a failed NM node takes quite some time > (~5 minutes) > > Is there a configurable setting for this? I need a more responsive cluster. > > Thank you, Caesar. > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
