You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2017/04/13 14:38:42 UTC
[jira] [Comment Edited] (AMBARI-20682) Wait For DataNodes To
Shutdown During a Rolling Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15967627#comment-15967627 ]
Dmitry Lysnichenko edited comment on AMBARI-20682 at 4/13/17 2:38 PM:
----------------------------------------------------------------------
To https://git-wip-us.apache.org/repos/asf/ambari.git
caad3e77c8..f02dac92cc branch-2.5 -> branch-2.5
ac75f1dacc..273dfcac02 trunk -> trunk
was (Author: dmitriusan):
To https://git-wip-us.apache.org/repos/asf/ambari.git
caad3e77c8..f02dac92cc branch-2.5 -> branch-2.5
> Wait For DataNodes To Shutdown During a Rolling Upgrade
> -------------------------------------------------------
>
> Key: AMBARI-20682
> URL: https://issues.apache.org/jira/browse/AMBARI-20682
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.2
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20682.patch
>
>
> During a rolling upgrade (especially on a large, heavily used cluster), the DataNodes do not shutdown immediately. However, they do de-register from the NameNode which tricks Ambari into thinking that they are down.
> Since the rolling upgrade uses a {{RESTART}} command, we attempt to start the DataNode back up before the daemon has shutdown:
> {code}
> 2017-03-14 05:00:25,602 - call['/usr/hdp/current/hadoop-hdfs-datanode/bin/hdfs dfsadmin -fs hdfs://c1ha -shutdownDatanode 0.0.0.0:8010 upgrade'] {'user': 'hdfs'}
> 2017-03-14 05:00:28,438 - call returned (0, 'Submitted a shutdown request to datanode 0.0.0.0:8010')
> 2017-03-14 05:00:28,438 - Execute['/usr/hdp/current/hadoop-hdfs-datanode/bin/hdfs dfsadmin -fs hdfs://c1ha -D ipc.client.connect.max.retries=5 -D ipc.client.connect.retry.interval=1000 -getDatanodeInfo 0.0.0.0:8010'] {'tries': 1, 'user': 'hdfs'}
> 2017-03-14 05:00:35,976 - DataNode has successfully shutdown for upgrade.
> {code}
> Even though ~ 6 seconds have passed, the daemon is still running as it drains. Therefore, we attempt to start it which causes a NOOP.
> Instead, we should also monitor for the PID.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)