Merge pull request #184636 from nicjohn79/patch-6

Update hdinsight-supported-node-configuration.md

Author: Court72

articles/hdinsight/hdinsight-supported-node-configuration.md

@@ -40,34 +40,22 @@ For more information on the specifications of each VM type, see the following do
 * [Memory optimized virtual machine sizes: Dv2 series 11-15](../virtual-machines/dv2-dsv2-series-memory.md)
 * [General purpose virtual machine sizes: Av2 series 1-8](../virtual-machines/av2-series.md)
 
-### All supported regions except Brazil south and Japan west
+### All supported regions
 
 > [!Note]
 > To get the SKU identifier for use in powershell and other scripts, add `Standard_` to the beginning of all of the VM SKUs in the tables below. For example, `D12_v2` would become `Standard_D12_v2`.
 
 | Cluster type                            | Hadoop | HBase  | Interactive Query | Storm | Spark                | Kafka                                |
 |-----------------------------------------|--------|--------|-------------------|-------|----------------------|--------------------------------------|
-| Head: default VM size                   | D12_v2 | D12_v2 | D13_v2            | A4_v2 | D12_v2, <br/>D13_v2* | D3_v2                                |
+| Head: default VM size                   | E4_v3 | E4_v3 | D13_v2            | A4_v2 | E8_v3, <br/>D13_v2* | E4_v3                                |
 | Head: minimum recommended VM sizes      | D5_v2  | D3_v2  | D13_v2            | A4_v2 | D12_v2, <br/>D13_v2* | D3_v2                                |
-| Worker: default VM size                 | D4_v2  | D4_v2  | D14_v2            | D3_v2 | D13_v2               | 4 D12_v2 with 2 S30 disks per broker |
+| Worker: default VM size                 | E8_v3  | E4_v3  | D14_v2            | D3_v2 | E8_v3               | 4 E4_v3 with 2 S30 disks per broker |
 | Worker: minimum recommended VM sizes    | D5_v2  | D3_v2  | D13_v2            | D3_v2 | D12_v2               | D3_v2                                |
 | ZooKeeper: default VM size              |        | A4_v2  | A4_v2             | A4_v2 |                      | A4_v2                                |
 | ZooKeeper: minimum recommended VM sizes |        | A4_v2  | A4_v2             | A2_v2 |                      | A4_v2                                |
 
 \* = VM Sizes for Spark Enterprise Security Package (ESP) clusters
 
-### Brazil south and Japan west only
-
-| Cluster type                            | Hadoop | HBase | Interactive Query | Storm | Spark  |
-|-----------------------------------------|--------|-------|-------------------|-------|--------|
-| Head: default VM size                   | D12    | D12   | D13               | A4_v2 | D12    |
-| Head: minimum recommended VM sizes      | D5_v2  | D3_v2 | D13_v2            | A4_v2 | D12_v2 |
-| Worker: default VM size                 | D4     | D4    | D14               | D3    | D13    |
-| Worker: minimum recommended VM sizes    | D5_v2  | D3_v2 | D13_v2            | D3_v2 | D12_v2 |
-| ZooKeeper: default VM size              |        | A4_v2 | A4_v2             | A4_v2 |        |
-| ZooKeeper: minimum recommended VM sizes |        | A4_v2 | A4_v2             | A4_v2 |        |
-
-
 > [!NOTE]
 > - Head is known as *Nimbus* for the Storm cluster type.
 > - Worker is known as *Supervisor* for the Storm cluster type.

articles/hdinsight/hdinsight-upgrade-cluster.md

@@ -50,7 +50,7 @@ For more information about database backup and restore, see [Recover a database
 As mentioned above, Microsoft recommends that HDInsight clusters be regularly migrated to the latest version in order to take advantage of new features and fixes. Please see the following list of reasons we would request that a cluster be deleted and redeployed:
 
 * The cluster version is [Retired](hdinsight-retired-versions.md) or in [Basic support](hdinsight-36-component-versioning.md) and you are having a cluster issue that would be resolved with a newer version.
-* The root cause of a cluster issue is determined to be related to an undersized VM. [View Microsoft's recommended node configuration](hdinsight-supported-node-configuration.md#all-supported-regions-except-brazil-south-and-japan-west).
+* The root cause of a cluster issue is determined to be related to an undersized VM. [View Microsoft's recommended node configuration](hdinsight-supported-node-configuration.md).
 * A customer opens a support case and the Microsoft engineering team determines the issue has already been fixed in a newer cluster version.
 * A default metastore database (Ambari, Hive, Oozie, Ranger) has reached it’s utilization limit. Microsoft will ask you to recreate the cluster using a [custom metastore](hdinsight-use-external-metadata-stores.md#custom-metastore) database.
 * The root cause of a cluster issue is due to an **Unsupported Operation**. Here are some of the common unsupported operations: