Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 6 Jul 2015 22:26:04 +0000 (UTC)
From: "MENG DING (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12691250.1390724095000.111531.1436221564779@Atlassian.JIRA>
In-Reply-To: <JIRA.12691250.1390724095000@Atlassian.JIRA>
References: <JIRA.12691250.1390724095000@Atlassian.JIRA>
 <JIRA.12691250.1390724095074@arcas>
Subject: [jira] [Updated] (YARN-1643) Make ContainersMonitor can support
 change monitoring size of an allocated container in NM side
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

MENG DING updated YARN-1643:
----------------------------
    Attachment: YARN-1643.2.patch

Attach patch for {{ContainersMonitorImpl}} for review.

Currently the {{ContainersMonitorImpl}} starts up one monitoring thread, and by default checks started and stopped containers every 3 seconds.

For resized containers, we  cannot use the same logic as the delay is unacceptable.

A wait/notify mechanism is implemented such that as soon as a {{CHANGE_MONITORING_CONTAINER_RESOURCE}} event is received, the monitor cycle is immediately triggered.

> Make ContainersMonitor can support change monitoring size of an allocated container in NM side
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-1643
>                 URL: https://issues.apache.org/jira/browse/YARN-1643
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>            Reporter: Wangda Tan
>            Assignee: MENG DING
>         Attachments: YARN-1643.1.patch, YARN-1643.2.patch
>
>


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)