Skip to content

Commit 431e7d6

Browse files
author
Sreekanth Iyer (Ushta Te Consultancy Services)
committed
Added link for the new page
1 parent 9590060 commit 431e7d6

File tree

3 files changed

+21
-7
lines changed

3 files changed

+21
-7
lines changed

articles/hdinsight/hdinsight-custom-ambari-db.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to create HDInsight clusters with your own custom Apache
44
ms.service: azure-hdinsight
55
ms.custom: hdinsightactive
66
ms.topic: how-to
7-
ms.date: 09/06/2024
7+
ms.date: 12/27/2024
88
---
99
# Set up HDInsight clusters with a custom Ambari DB
1010

@@ -72,6 +72,8 @@ az deployment group create --name HDInsightAmbariDBDeployment \
7272
> Please use the following recommended SQL DB and Headnode VM for your HDInsight cluster. Please don't use default Ambari DB (S0) for any production environment.
7373
>
7474
75+
> [!NOTE]
76+
> You can use Managed Identity to authenticate with SQL database for Ambari. For more information, see [Use Managed Identity for SQL Database authentication in Azure HDInsight](./use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md)
7577
7678
## Database and Headnode sizing
7779

articles/hdinsight/hdinsight-hadoop-provision-linux-clusters.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -140,17 +140,23 @@ If you want to retain your Hive tables after you delete a HDInsight cluster, use
140140

141141
A HDInsight metastore that is created for one HDInsight cluster version can't be shared across different HDInsight cluster versions. For a list of HDInsight versions, see [Supported HDInsight versions](hdinsight-component-versioning.md#supported-hdinsight-versions).
142142

143+
You can use Managed Identity to authenticate with SQL database for Hive. For more information, see [Use Managed Identity for SQL Database authentication in Azure HDInsight](./use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md)
144+
143145
> [!IMPORTANT]
144146
> 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.
145147
146148
#### SQL database for Oozie
147149

148150
To increase performance when using Oozie, use a custom metastore. A metastore can also provide access to Oozie job data after you delete your cluster.
149151

152+
You can use Managed Identity to authenticate with SQL database for Oozie. For more information, see [Use Managed Identity for SQL Database authentication in Azure HDInsight](./use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md)
153+
150154
#### SQL database for Ambari
151155

152156
Ambari is used to monitor HDInsight clusters, make configuration changes, and store cluster management information as well as job history. The custom Ambari DB feature allows you to deploy a new cluster and setup Ambari in an external database that you manage. For more information, see [Custom Ambari DB](./hdinsight-custom-ambari-db.md).
153157

158+
You can use Managed Identity to authenticate with SQL database for Ambari. For more information, see [Use Managed Identity for SQL Database authentication in Azure HDInsight](./use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md)
159+
154160
> [!IMPORTANT]
155161
> You cannot reuse a custom Oozie metastore. To use a custom Oozie metastore, you must provide an empty Azure SQL Database when creating the HDInsight cluster.
156162

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

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Use external metadata stores with Azure HDInsight clusters.
44
ms.service: azure-hdinsight
55
ms.topic: how-to
66
ms.custom: hdinsightactive
7-
ms.date: 07/12/2024
7+
ms.date: 27/12/2024
88
---
99

1010
# Use external metadata stores in Azure HDInsight
@@ -116,16 +116,22 @@ When using a custom Oozie metastore database, you have the ability to change the
116116

117117
To update the Oozie metastore password:
118118
1. Open the Ambari UI.
119-
2. Click **Services --> Oozie --> Configs --> Database**.
120-
3. Update the **Database Password** fields to the new SQL server database password.
121-
4. Click the **Test Connection** button to make sure the new password works.
122-
5. Click the **Save** button.
123-
6. Follow the Ambari prompts to save the config and Restart the required services.
119+
1. Click **Services --> Oozie --> Configs --> Database**.
120+
1. Update the **Database Password** fields to the new SQL server database password.
121+
1. Click the **Test Connection** button to make sure the new password works.
122+
1. Click the **Save** button.
123+
1. Follow the Ambari prompts to save the config and Restart the required services.
124+
125+
> [!NOTE]
126+
> You can use Managed Identity to authenticate with SQL database for Oozie. For more information, see [Use Managed Identity for SQL Database authentication in Azure HDInsight](./use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md)
124127
125128
## Custom Ambari DB
126129

127130
To use your own external database with Apache Ambari on HDInsight, see [Custom Apache Ambari database](hdinsight-custom-ambari-db.md).
128131

132+
> [!NOTE]
133+
> You can use Managed Identity to authenticate with SQL database for Ambari. For more information, see [Use Managed Identity for SQL Database authentication in Azure HDInsight](./use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md)
134+
129135
## Next steps
130136

131137
* [Set up clusters in HDInsight with Apache Hadoop, Apache Spark, Apache Kafka, and more](./hdinsight-hadoop-provision-linux-clusters.md)

0 commit comments

Comments
 (0)