[
https://issues.apache.org/jira/browse/AMBARI-20682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367121#comment-16367121
]
Hudson commented on AMBARI-20682:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8744 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8744/])
AMBARI-20682. Wait For DataNodes To Shutdown During a Rolling Upgrade
(aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c4bd3b9e46675ad411e9454c399d5e6a3fbcf156])
* (edit)
ambari-common/src/main/python/resource_management/libraries/script/script.py
* (edit)
ambari-funtest/src/test/resources/stacks/HDP/2.0.7/services/HIVE/package/scripts/mysql_service.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode_upgrade.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py
* (edit)
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/postgresql_service.py
* (edit)
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/mysql_service.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_datanode.py
AMBARI-20682. Wait For DataNodes To Shutdown During a Rolling Upgrade.
(aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=6474b32da2bf1d98d9ab4e0c254eee0ecc2b70f4])
* (edit)
ambari-common/src/main/python/resource_management/libraries/script/script.py
> 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
(v7.6.3#76005)
