Skip to content

Commit f77bd6d

Browse files
author
Sreekanth Iyer (Ushta Te Consultancy Services)
committed
Resolved review Comments
1 parent aa5bdc5 commit f77bd6d

7 files changed

+11
-11
lines changed

articles/hdinsight/apache-ambari-email.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ In this tutorial, you learn how to:
3636

3737
1. From the Overview page, click **Open SaaS Account on publisher’s site**, to go the SendGrid webpage for your account.
3838

39-
:::image type="content" source="./media/apache-ambari-email/azure-portal-sendgrid-manage.png" alt-text="SendGrid overview in azure portal.":::
39+
:::image type="content" source="./media/apache-ambari-email/azure-portal-sendgrid-manage.png" alt-text="SendGrid overview in Azure portal.":::
4040

4141
1. From the left menu, navigate to your **Settings** and then **API Keys**.
4242

articles/hdinsight/apache-ambari-usage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.date: 06/15/2024
88

99
# Apache Ambari usage in Azure HDInsight
1010

11-
HDInsight uses Apache Ambari for cluster deployment and management. Ambari agents run on every node provide if headnode, worker node, zookeeper, and edgenode. Ambari server runs only on headnode. Only one instance of Ambari server shall run at one time. This is controlled by HDInsight failover controller. When one of the headnodes is down for reboot or maintenance, the other headnode will become active and Ambari server on the second headnode will be started.
11+
HDInsight uses Apache Ambari for cluster deployment and management. Ambari agents run on every node provided if headnode, worker node, zookeeper, and edgenode are present. Ambari server runs only on headnode. Only one instance of Ambari server shall run at one time. This is controlled by HDInsight failover controller. When one of the headnodes is down for reboot or maintenance, the other headnode will become active and Ambari server on the second headnode will be started.
1212

1313
All cluster configuration should be done through the [Ambari UI](./hdinsight-hadoop-manage-ambari.md), any local change will be overwritten when the node is restarted.
1414

articles/hdinsight/cluster-availability-monitor-logs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -110,9 +110,9 @@ You can also view all alerts that have fired, grouped by severity, by going to *
110110

111111
:::image type="content" source="media/cluster-availability-monitor-logs/hdi-portal-oms-alerts.png" alt-text="Log Analytics workspace alerts.":::
112112

113-
When you select on a severity group (i.e. **severity 1,** as highlighted above) will show records for all alerts of that severity that have fired like below:
113+
When you select on a severity group (i.e. **severity 1,** as highlighted above) it will show records for all alerts of that severity that have fired like below:
114114

115-
:::image type="content" source="media/cluster-availability-monitor-logs/portal-oms-alerts-sev1.png" alt-text="Log Analytics workspace severity one alert.":::
115+
:::image type="content" source="media/cluster-availability-monitor-logs/portal-oms-alerts-sev1.png" alt-text="Screenshot showing Log Analytics workspace severity one alert.":::
116116

117117
## Next steps
118118

articles/hdinsight/domain-joined/apache-domain-joined-manage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 06/15/2024
1010

1111
Learn the users and the roles in HDInsight Enterprise Security Package (ESP), and how to manage ESP clusters.
1212

13-
## Use VSCode to link to domain joined cluster
13+
## Use VS Code to link to domain joined cluster
1414

1515
You can link a normal cluster by using Apache Ambari managed username, also link a security Apache Hadoop cluster by using domain username (such as: `[email protected]`).
1616

articles/hdinsight/domain-joined/apache-domain-joined-run-kafka.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Create a Ranger policy for **sales_user** and **marketing_user**.
6666

6767
|Setting |Suggested value |
6868
|---------|---------|
69-
|Policy Name | HDinsight marketing policy |
69+
|Policy Name | HDInsight marketing policy |
7070
|Topic | `marketingspend` |
7171
|Select User | marketing_user1 |
7272
|Permissions | publish, consume, create |

articles/hdinsight/domain-joined/general-guidelines.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ When hierarchical name space in not enabled:
6666
If the url auth is enabled:
6767

6868
* The config will contain what prefixes are covered in the url auth (like `adl://`).
69-
* If the access is for this url, then Ranger will check if the user is in the allow list.
69+
* If the access is for this url, then Ranger will check if the user is in the allowlist.
7070
* Ranger won't check any of the fine grained policies.
7171

7272
### Manage Ranger audit logs

articles/hdinsight/domain-joined/troubleshoot-domainnotfound.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,23 +20,23 @@ Incorrect DNS settings.
2020

2121
## Resolution
2222

23-
When the domain joined clusters are deployed, HDI creates an internal user name and password in AAD DS (for each cluster) and joins all the cluster nodes to this domain. The domain join is accomplished using Samba tools. Ensure the following prerequisites are met:
23+
When the domain joined clusters are deployed, HDI creates an internal user name and password in Azure Active Directory Domain Services (for each cluster) and joins all the cluster nodes to this domain. The domain join is accomplished using Samba tools. Ensure the following prerequisites are met:
2424

2525
* The domain name should resolve through DNS.
2626
* The IP address of the domain controllers should be set in the DNS settings for the virtual network where the cluster is being deployed.
27-
* If the virtual network is peered with the virtual network of AAD DS, then it has to be done manually.
27+
* If the virtual network is peered with the virtual network of Azure Active Directory Domain Services, then it has to be done manually.
2828
* If you're using DNS forwarders, the domain name must resolve correctly within the virtual network.
2929
* Security policies (NSGs) shouldn't block the domain join.
3030

3131
### Additional debugging steps
3232

33-
* Deploy a windows VM in the same subnet, domain join the machine using a username and password (this can be done through the control panel UI), or
33+
* Deploy a windows VM in the same subnet, domain join the machine using a username and password (which can be done through the control panel UI), or
3434

3535
* Deploy an Ubuntu VM in the same subnet and domain join the machine
3636
* SSH into the machine
3737
* sudo su
3838
* Run the [script](./sample-script.md) with username and password
39-
* The script will ping, create the required configuration files and then domain. If it succeeds, your DNS settings are good.
39+
* The script pings, create the required configuration files and then domain. If it succeeds, your DNS settings are good.
4040

4141
## Next steps
4242

0 commit comments

Comments
 (0)