Merge pull request #197323 from kcheeeung/exmeta

Move notice up for HDI default metastore and update anchor

Author: tamarakhader

articles/hdinsight/hdinsight-faq.yml

@@ -120,7 +120,7 @@ sections:
       - question: |
           How can I estimate the size of a Hive metastore database?
         answer: |
-          A Hive metastore is used to store the metadata for data sources that are used by the Hive server. The size requirements depend partly on the number and complexity of your Hive data sources. These items can't be estimated up front. As outlined in [Hive metastore guidelines](hdinsight-use-external-metadata-stores.md#hive-metastore-guidelines), you can start with a S2 tier. The tier provides 50 DTU and 250 GB of storage, and if you see a bottleneck, scale up the database.
+          A Hive metastore is used to store the metadata for data sources that are used by the Hive server. The size requirements depend partly on the number and complexity of your Hive data sources. These items can't be estimated up front. As outlined in [Hive metastore guidelines](hdinsight-use-external-metadata-stores.md#apache-hive-metastore-guidelines), you can start with a S2 tier. The tier provides 50 DTU and 250 GB of storage, and if you see a bottleneck, scale up the database.
           
       - question: |
           Do you support any other database other than Azure SQL Database as an external metastore?

articles/hdinsight/hdinsight-use-external-metadata-stores.md

@@ -4,7 +4,7 @@ description: Use external metadata stores with Azure HDInsight clusters.
 ms.service: hdinsight
 ms.topic: how-to
 ms.custom: hdinsightactive
-ms.date: 04/01/2022
+ms.date: 05/05/2022
 ---
 
 # Use external metadata stores in Azure HDInsight
@@ -22,6 +22,9 @@ There are two ways you can set up a metastore for your HDInsight clusters:
 
 ## Default metastore
 
+> [!IMPORTANT]
+> The default metastore provides a basic tier Azure SQL Database with only **5 DTU and 2 GB data max size (NOT UPGRADEABLE)**! Use this for QA and testing purposes only. **For production or large workloads, we recommend migrating to an external metastore!**
+
 By default, HDInsight creates a metastore with every cluster type. You can instead specify a custom metastore. The default metastore includes the following considerations:
 
 * No additional cost. HDInsight creates a metastore with every cluster type without any additional cost to you.
@@ -32,14 +35,11 @@ By default, HDInsight creates a metastore with every cluster type. You can inste
 
 * Default metastore is recommended only for simple workloads. Workloads that don't require multiple clusters and don't need metadata preserved beyond the cluster's lifecycle.
 
-> [!IMPORTANT]
-> The default metastore provides an Azure SQL Database with a **basic tier 5 DTU limit (not upgradeable)**! Suitable for basic testing purposes. For large or production workloads, we recommend migrating to an external metastore.
-
 ## Custom metastore
 
 HDInsight also supports custom metastores, which are recommended for production clusters:
 
-* You specify your own Azure SQL Database as the metastore.
+* You specify your own **Azure SQL Database** as the metastore.
 
 * The lifecycle of the metastore isn't tied to a clusters lifecycle, so you can create and delete clusters without losing metadata. Metadata such as your Hive schemas will persist even after you delete and re-create the HDInsight cluster.
 
@@ -59,7 +59,7 @@ Create or have an existing Azure SQL Database before setting up a custom Hive me
 
 While creating the cluster, HDInsight service needs to connect to the external metastore and verify your credentials. Configure Azure SQL Database firewall rules to allow Azure services and resources to access the server. Enable this option in the Azure portal by selecting **Set server firewall**. Then select **No** underneath **Deny public network access**, and **Yes** underneath **Allow Azure services and resources to access this server** for Azure SQL Database. For more information, see [Create and manage IP firewall rules](/azure/azure-sql/database/firewall-configure#use-the-azure-portal-to-manage-server-level-ip-firewall-rules)
 
-Private endpoints for SQL stores is only supported on the clusters created with `outbound` ResourceProviderConnection. To learn more, see this [documentationa](./hdinsight-private-link.md).
+Private endpoints for SQL stores is only supported on the clusters created with `outbound` ResourceProviderConnection. To learn more, see this [documentation](./hdinsight-private-link.md).
 
 :::image type="content" source="./media/hdinsight-use-external-metadata-stores/configure-azure-sql-database-firewall1.png" alt-text="set server firewall button":::
 
@@ -71,7 +71,7 @@ You can point your cluster to a previously created Azure SQL Database at any tim
 
 :::image type="content" source="./media/hdinsight-use-external-metadata-stores/azure-portal-cluster-storage-metastore.png" alt-text="HDInsight Hive Metadata Store Azure portal":::
 
-## Hive metastore guidelines
+## Apache Hive metastore guidelines
 
 > [!NOTE]
 > Use a custom metastore whenever possible, to help separate compute resources (your running cluster) and metadata (stored in the metastore). Start with the S2 tier, which provides 50 DTU and 250 GB of storage. If you see a bottleneck, you can scale the database up.
@@ -92,7 +92,7 @@ You can point your cluster to a previously created Azure SQL Database at any tim
 
 * In HDInsight 4.0 if you would like to Share the metastore between Hive and Spark, you can do so by changing the property metastore.catalog.default to hive in your Spark cluster. You can find this property in Ambari Advanced spark2-hive-site-override. It’s important to understand that sharing of metastore only works for external hive tables, this will not work if you have internal/managed hive tables or ACID tables.  
 
-### Updating the custom Hive metastore password
+## Updating the custom Hive metastore password
 When using a custom Hive metastore database, you have the ability to change the SQL DB password. If you change the password for the custom metastore, the Hive services will not work until you update the password in the HDInsight cluster. 
 
 To update the Hive metastore password:
@@ -109,7 +109,7 @@ Apache Oozie is a workflow coordination system that manages Hadoop jobs. Oozie s
 
 For instructions on creating an Oozie metastore with Azure SQL Database, see [Use Apache Oozie for workflows](hdinsight-use-oozie-linux-mac.md).
 
-### Updating the custom Oozie metastore password
+## Updating the custom Oozie metastore password
 When using a custom Oozie metastore database, you have the ability to change the SQL DB password. If you change the password for the custom metastore, the Oozie services will not work until you update the password in the HDInsight cluster. 
 
 To update the Oozie metastore password: