Skip to content

Commit d0fbad0

Browse files
committed
ts_ambari8
1 parent 38bfc55 commit d0fbad0

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/hdinsight/hdinsight-scaling-best-practices.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: ashish
66
ms.reviewer: jasonh
77
ms.service: hdinsight
88
ms.topic: conceptual
9-
ms.date: 11/22/2019
9+
ms.date: 02/05/2020
1010
---
1111

1212
# Scale Azure HDInsight clusters
@@ -212,6 +212,10 @@ If your clusters get stuck in safe mode frequently when scaling down to fewer th
212212
213213
Retaining three worker nodes is more costly than scaling down to only one worker node, but it will prevent your cluster from getting stuck in safe mode.
214214
215+
### Scale HDInsight down to one worker node
216+
217+
Even when the cluster is scaled down to 1 node, worker node 0 will still survive. Worker node 0 can never be decommissioned.
218+
215219
#### Run the command to leave safe mode
216220
217221
The final option is to execute the leave safe mode command. If you know that the reason for HDFS entering safe mode is because of Hive file under-replication, you can execute the following command to leave safe mode:

0 commit comments

Comments
 (0)