Re: why the default value of 'yarn.resourcemanager.container.liveness-monitor.interval-ms' in yarn-default.xml is so high?

Hi Tanvir! Although an application may request for that node, a container won't be scheduled until the nodemanager sends a heartbeat. If the application hasn't specified a preference for that node, then whichever node heartbeats next, will be used to launch a container. HTH Ravi On Thu, Nov 3,

Re: why the default value of 'yarn.resourcemanager.container.liveness-monitor.interval-ms' in yarn-default.xml is so high?

Thank you Ravi for your reply. I found one parameter 'yarn.resourcemanager.nm.liveness-monitor.interval-ms' (default value=1000ms) in yarn-default.xml (v2.4.1) which determines how often to check that node managers are still alive. So RM is checking heartbeat of NM every second but it takes 10 min

why the default value of 'yarn.resourcemanager.container.liveness-monitor.interval-ms' in yarn-default.xml is so high?

Hello, Can anyone please tell me why the default value of ' yarn.resourcemanager.container.liveness-monitor.interval-ms' in yarn-default.xml is so high? This parameter determines "How often to check that