Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 4 Jul 2016 18:25:11 +0000 (UTC)
From: "Junping Du (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12937171.1454709348000.21059.1467656711100@Atlassian.JIRA>
In-Reply-To: <JIRA.12937171.1454709348000@Atlassian.JIRA>
References: <JIRA.12937171.1454709348000@Atlassian.JIRA> <JIRA.12937171.1454709348730@arcas>
Subject: [jira] [Commented] (YARN-4676) Automatic and Asynchronous
 Decommissioning Nodes Status Tracking
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Mon, 04 Jul 2016 18:25:13 -0000


    [ https://issues.apache.org/jira/browse/YARN-4676?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15361=
687#comment-15361687 ]=20

Junping Du commented on YARN-4676:
----------------------------------

Hi [~rkanter], thanks for pushing on this patch. As we talked on the last d=
ay of Hadoop Summit, do you try previous function for graceful decommission=
 (client side tracking) still works normal after applying this patch? If no=
t, I can help to verify it here.

> Automatic and Asynchronous Decommissioning Nodes Status Tracking
> ----------------------------------------------------------------
>
>                 Key: YARN-4676
>                 URL: https://issues.apache.org/jira/browse/YARN-4676
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 2.8.0
>            Reporter: Daniel Zhi
>            Assignee: Daniel Zhi
>              Labels: features
>         Attachments: GracefulDecommissionYarnNode.pdf, GracefulDecommissi=
onYarnNode.pdf, YARN-4676.004.patch, YARN-4676.005.patch, YARN-4676.006.pat=
ch, YARN-4676.007.patch, YARN-4676.008.patch, YARN-4676.009.patch, YARN-467=
6.010.patch, YARN-4676.011.patch, YARN-4676.012.patch, YARN-4676.013.patch,=
 YARN-4676.014.patch, YARN-4676.015.patch, YARN-4676.016.patch
>
>
> YARN-4676 implements an automatic, asynchronous and flexible mechanism to=
 graceful decommission
> YARN nodes. After user issues the refreshNodes request, ResourceManager a=
utomatically evaluates
> status of all affected nodes to kicks out decommission or recommission ac=
tions. RM asynchronously
> tracks container and application status related to DECOMMISSIONING nodes =
to decommission the
> nodes immediately after there are ready to be decommissioned. Decommissio=
ning timeout at individual
> nodes granularity is supported and could be dynamically updated. The mech=
anism naturally supports multiple
> independent graceful decommissioning =E2=80=9Csessions=E2=80=9D where eac=
h one involves different sets of nodes with
> different timeout settings. Such support is ideal and necessary for grace=
ful decommission request issued
> by external cluster management software instead of human.
> DecommissioningNodeWatcher inside ResourceTrackingService tracks DECOMMIS=
SIONING nodes status automatically and asynchronously after client/admin ma=
de the graceful decommission request. It tracks DECOMMISSIONING nodes statu=
s to decide when, after all running containers on the node have completed, =
will be transitioned into DECOMMISSIONED state. NodesListManager detect and=
 handle include and exclude list changes to kick out decommission or recomm=
ission as necessary.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org