You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: articles/hdinsight/hdinsight-debug-tez-ui.md
+34-35
Original file line number
Diff line number
Diff line change
@@ -22,15 +22,15 @@ ROBOTS: NOINDEX
22
22
The Tez UI is a web page that can be used to understand and debug jobs that use Tez as the execution engine on Windows-based HDInsight clusters. The Tez UI allows you to visualize the job as a graph of connected items, drill into each item, and retrieve statistics and logging information.
23
23
24
24
> [!IMPORTANT]
25
-
> The steps in this document require an HDInsight cluster that uses Windows. Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-32-and-33-nearing-deprecation-date).
25
+
> The steps in this document require an HDInsight cluster that uses Windows. Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-33-nearing-deprecation-date).
26
26
27
27
## Prerequisites
28
28
* A Windows-based HDInsight cluster. For steps on creating a new cluster, see [Get started using Windows-based HDInsight](hdinsight-hadoop-tutorial-get-started-windows.md).
29
-
29
+
30
30
> [!IMPORTANT]
31
31
> The Tez UI is only available on Windows-based HDInsight clusters created after February 8th, 2016.
32
-
>
33
-
>
32
+
>
33
+
>
34
34
* A Windows-based Remote Desktop client.
35
35
36
36
## Understanding Tez
@@ -53,90 +53,89 @@ Use the following steps to run a Hive query that will execute using Tez.
53
53
54
54
1. In a web browser, navigate to https://CLUSTERNAME.azurehdinsight.net, where **CLUSTERNAME** is the name of your HDInsight cluster.
55
55
2. From the menu at the top of the page, select the **Hive Editor**. This will display a page with the following example query.
56
-
56
+
57
57
Select * from hivesampletable
58
-
58
+
59
59
Erase the example query and replace it with the following.
60
-
60
+
61
61
set hive.execution.engine=tez;
62
62
select market, state, country from hivesampletable where deviceplatform='Android' group by market, country, state;
63
63
3. Select the **Submit** button. The **Job Session** section at the bottom of the page will display the status of the query. Once the status changes to **Completed**, select the **View Details** link to view the results. The **Job Output** should be similar to the following:
64
-
64
+
65
65
en-GB Hessen Germany
66
66
en-GB Kingston Jamaica
67
67
en-GB Nairobi Area Kenya
68
68
69
69
## Use the Tez UI
70
70
> [!NOTE]
71
71
> The Tez UI is only available from the desktop of the cluster head nodes, so you must use Remote Desktop to connect to the head nodes.
72
-
>
73
-
>
72
+
>
73
+
>
74
74
75
75
1. From the [Azure portal](https://portal.azure.com), select your HDInsight cluster. From the top of the HDInsight blade, select the **Remote Desktop** icon. This will display the remote desktop blade
2. From the Remote Desktop blade, select **Connect** to connect to the cluster head node. When prompted, use the cluster Remote Desktop user name and password to authenticate the connection.
> If you have not enabled Remote Desktop connectivity, provide a user name, password, and expiration date, then select **Enable** to enable Remote Desktop. Once it has been enabled, use the previous steps to connect.
84
-
>
85
-
>
84
+
>
85
+
>
86
86
3. Once connected, open Internet Explorer on the remote desktop, select the gear icon in the upper right of the browser, and then select **Compatibility View Settings**.
87
87
4. From the bottom of **Compatibility View Settings**, clear the check box for **Display intranet sites in Compatibility View** and **Use Microsoft compatibility lists**, and then select **Close**.
88
88
5. In Internet Explorer, browse to http://headnodehost:8188/tezui/#/. This will display the Tez UI
When the Tez UI loads, you will see a list of DAGs that are currently running, or have been ran on the cluster. The default view includes the Dag Name, Id, Submitter, Status, Start Time, End Time, Duration, Application ID, and Queue. More columns can be added using the gear icon at the right of the page.
93
-
93
+
94
94
If you have only one entry, it will be for the query that you ran in the previous section. If you have multiple entries, you can search by entering search criteria in the fields above the DAGs, then hit **Enter**.
95
95
6. Select the **Dag Name** for the most recent DAG entry. This will display information about the DAG, as well as the option to download a zip of JSON files that contain information about the DAG.
7. Above the **DAG Details** are several links that can be used to display information about the DAG.
99
-
99
+
100
100
***DAG Counters** displays counters information for this DAG.
101
101
***Graphical View** displays a graphical representation of this DAG.
102
102
***All Vertices** displays a list of the vertices in this DAG.
103
103
***All Tasks** displays a list of the tasks for all vertices in this DAG.
104
104
***All TaskAttempts** displays information about the attempts to run tasks for this DAG.
105
-
105
+
106
106
> [!NOTE]
107
107
> If you scroll the column display for Vertices, Tasks and TaskAttempts, notice that there are links to view **counters** and **view or download logs** for each row.
108
-
>
109
-
>
110
-
108
+
>
109
+
>
110
+
111
111
If there was a failure with the job, the DAG Details will display a status of FAILED, along with links to information about the failed task. Diagnostics information will be displayed beneath the DAG details.
112
112
8. Select **Graphical View**. This displays a graphical representation of the DAG. You can place the mouse over each vertex in the view to display information about it.
9. Clicking on a vertex will load the **Vertex Details** for that item. Click on the **Map 1** vertex to display details for this item. Select **Confirm** to confirm the navigation.
10. Note that you now have links at the top of the page that are related to vertices and tasks.
119
-
119
+
120
120
> [!NOTE]
121
121
> You can also arrive at this page by going back to **DAG Details**, selecting **Vertex Details**, and then selecting the **Map 1** vertex.
122
-
>
123
-
>
124
-
122
+
>
123
+
>
124
+
125
125
***Vertex Counters** displays counter information for this vertex.
126
126
***Tasks** displays tasks for this vertex.
127
127
***Task Attempts** displays information about attempts to run tasks for this vertex.
128
128
***Sources & Sinks** displays data sources and sinks for this vertex.
129
-
129
+
130
130
> [!NOTE]
131
131
> As with the previous menu, you can scroll the column display for Tasks, Task Attempts, and Sources & Sinks__ to display links to more information for each item.
132
-
>
133
-
>
132
+
>
133
+
>
134
134
11. Select **Tasks**, and then select the item named **00_000000**. This will display **Task Details** for this task. From this screen, you can view **Task Counters** and **Task Attempts**.
Copy file name to clipboardexpand all lines: articles/hdinsight/hdinsight-hadoop-access-yarn-app-logs-linux.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ ms.author: larryfr
23
23
This document explains how to access the logs for YARN (Yet Another Resource Negotiator) applications that have finished on a Hadoop cluster in Azure HDInsight.
24
24
25
25
> [!IMPORTANT]
26
-
> The steps in this document require an HDInsight cluster that uses Linux. Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-32-and-33-nearing-deprecation-date).
26
+
> The steps in this document require an HDInsight cluster that uses Linux. Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-33-nearing-deprecation-date).
27
27
28
28
## Prerequisites
29
29
* A Linux-based HDInsight cluster.
@@ -54,7 +54,7 @@ Application logs (and the associated container logs) are critical in debugging p
54
54
55
55
In that location, *user* is the name of the user who started the application, and *applicationId* is the unique identifier of an application as assigned by the YARN RM.
56
56
57
-
The aggregated logs are not directly readable, as they are written in a [TFile][T-file], [binary format][binary-format] indexed by container. You must use the YARN ResourceManager logs or CLI tools to view these logs as plain text for applications or containers of interest.
57
+
The aggregated logs are not directly readable, as they are written in a [TFile][T-file], [binary format][binary-format] indexed by container. You must use the YARN ResourceManager logs or CLI tools to view these logs as plain text for applications or containers of interest.
58
58
59
59
## YARN CLI tools
60
60
@@ -74,12 +74,12 @@ Once you have created an SSH tunnel, use the following steps to view the YARN lo
74
74
75
75
1. In your web browser, navigate to https://CLUSTERNAME.azurehdinsight.net. Replace CLUSTERNAME with the name of your HDInsight cluster.
76
76
2. From the list of services on the left, select **YARN**.
77
-
77
+
78
78

79
79
3. From the **Quick Links** dropdown, select one of the cluster head nodes and then select **ResourceManager Log**.
Copy file name to clipboardexpand all lines: articles/hdinsight/hdinsight-hadoop-access-yarn-app-logs.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -23,8 +23,8 @@ ROBOTS: NOINDEX
23
23
This topic explains how to access the logs for YARN (Yet Another Resource Negotiator) applications that have finished on a Windows-based Hadoop cluster in Azure HDInsight
24
24
25
25
> [!IMPORTANT]
26
-
> The information in this document applies only to Windows-based HDInsight clusters. Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-32-and-33-nearing-deprecation-date). For information on accessing YARN logs on Linux-based HDInsight clusters, see [Access YARN application logs on Linux-based Hadoop on HDInsight](hdinsight-hadoop-access-yarn-app-logs-linux.md)
27
-
>
26
+
> The information in this document applies only to Windows-based HDInsight clusters. Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-33-nearing-deprecation-date). For information on accessing YARN logs on Linux-based HDInsight clusters, see [Access YARN application logs on Linux-based Hadoop on HDInsight](hdinsight-hadoop-access-yarn-app-logs-linux.md)
27
+
>
28
28
29
29
30
30
### Prerequisites
@@ -66,9 +66,9 @@ The aggregated logs are not directly readable, as they are written in a [TFile][
66
66
67
67
68
68
## YARN ResourceManager UI
69
-
The YARN ResourceManager UI runs on the cluster headnode, and can be accessed through the Azure portal dashboard:
69
+
The YARN ResourceManager UI runs on the cluster headnode, and can be accessed through the Azure portal dashboard:
70
70
71
-
1. Sign in to [Azure portal](https://portal.azure.com/).
71
+
1. Sign in to [Azure portal](https://portal.azure.com/).
72
72
2. On the left menu, click **Browse**, click **HDInsight Clusters**, click a Windows-based cluster that you want to access the YARN application logs.
73
73
3. On the top menu, click **Dashboard**. You will see a page opened on a new browser tab called **HDInsight Query Console**.
74
74
4. From **HDInsight Query Console**, click **Yarn UI**.
Copy file name to clipboardexpand all lines: articles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ For **Linux-based clusters**: [https://hdiconfigactions.blob.core.windows.net/li
43
43
For **Windows-based clusters**: [https://hdiconfigactions.blob.core.windows.net/setupcustomhivelibsv01/setup-customhivelibs-v01.ps1](https://hdiconfigactions.blob.core.windows.net/setupcustomhivelibsv01/setup-customhivelibs-v01.ps1)
44
44
45
45
> [!IMPORTANT]
46
-
> Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-32-and-33-nearing-deprecation-date).
46
+
> Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-33-nearing-deprecation-date).
Copy file name to clipboardexpand all lines: articles/hdinsight/hdinsight-hadoop-collect-debug-heap-dump-linux.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Heap dumps contain a snapshot of the application's memory, including the values
27
27
28
28
29
29
> [!IMPORTANT]
30
-
> The steps in this document only work with HDInsight clusters that use Linux. Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-32-and-33-nearing-deprecation-date).
30
+
> The steps in this document only work with HDInsight clusters that use Linux. Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-33-nearing-deprecation-date).
31
31
32
32
## <aname="whichServices"></a>Services
33
33
You can enable heap dumps for the following services:
Heap dumps contain a snapshot of the application's memory, including the values of variables
26
-
at the time the dump was created. So they are very useful for diagnosing problems that occur
27
-
at run-time. Heap dumps can be automatically collected for Hadoop services and placed inside
28
-
the Azure Blob storage account of a user under HDInsightHeapDumps/.
29
-
30
-
The collection of heap dumps for various services must be enabled for services on individual
31
-
clusters. The default for this feature is to be off for a cluster. These heap dumps can be
32
-
large, so it is advisable to monitor the Blob storage account where they are being saved
25
+
Heap dumps contain a snapshot of the application's memory, including the values of variables
26
+
at the time the dump was created. So they are very useful for diagnosing problems that occur
27
+
at run-time. Heap dumps can be automatically collected for Hadoop services and placed inside
28
+
the Azure Blob storage account of a user under HDInsightHeapDumps/.
29
+
30
+
The collection of heap dumps for various services must be enabled for services on individual
31
+
clusters. The default for this feature is to be off for a cluster. These heap dumps can be
32
+
large, so it is advisable to monitor the Blob storage account where they are being saved
33
33
once the collection has been enabled.
34
34
35
35
> [!IMPORTANT]
36
-
> Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-32-and-33-nearing-deprecation-date). The information in this article only applies to Windows-based HDInsight.
37
-
> For information on Linux-based HDInsight, see [Enable heap dumps for Hadoop services on
36
+
> Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-33-nearing-deprecation-date). The information in this article only applies to Windows-based HDInsight.
37
+
> For information on Linux-based HDInsight, see [Enable heap dumps for Hadoop services on
Copy file name to clipboardexpand all lines: articles/hdinsight/hdinsight-hadoop-create-linux-clusters-azure-cli.md
+1-2
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ ms.author: larryfr
26
26
The steps in this document walk-through creating a HDInsight 3.5 cluster using the Azure CLI 1.0.
27
27
28
28
> [!IMPORTANT]
29
-
> Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight 3.2 and 3.3 deprecation](hdinsight-component-versioning.md#hdi-version-32-and-33-nearing-deprecation-date).
29
+
> Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight 3.2 and 3.3 deprecation](hdinsight-component-versioning.md#hdi-version-33-nearing-deprecation-date).
30
30
31
31
32
32
## Prerequisites
@@ -144,4 +144,3 @@ Now that you have successfully created an HDInsight cluster using the Azure CLI,
144
144
*[Develop Java topologies for Storm on HDInsight](hdinsight-storm-develop-java-topology.md)
145
145
*[Use Python components in Storm on HDInsight](hdinsight-storm-develop-python-topology.md)
146
146
*[Deploy and monitor topologies with Storm on HDInsight](hdinsight-storm-deploy-monitor-topology-linux.md)
Copy file name to clipboardexpand all lines: articles/hdinsight/hdinsight-hadoop-create-linux-clusters-curl-rest.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Learn how to create an HDInsight cluster using an Azure Resource Manager templat
28
28
The Azure REST API allows you to perform management operations on services hosted in the Azure platform, including the creation of new resources such as HDInsight clusters.
29
29
30
30
> [!IMPORTANT]
31
-
> Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-32-and-33-nearing-deprecation-date).
31
+
> Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-33-nearing-deprecation-date).
Copy file name to clipboardexpand all lines: articles/hdinsight/hdinsight-hadoop-customize-cluster-linux.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ HDInsight provides a configuration option called **Script Action** that invokes
26
26
> [!IMPORTANT]
27
27
> The ability to use script actions on an already running cluster is only available for Linux-based HDInsight clusters.
28
28
>
29
-
> Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-32-and-33-nearing-deprecation-date).
29
+
> Linux is the only operating system used on HDInsight version 3.4 or greater. For more information, see [HDInsight Deprecation on Windows](hdinsight-component-versioning.md#hdi-version-33-nearing-deprecation-date).
30
30
31
31
32
32
Script actions can also be published to the Azure Marketplace as an HDInsight application. Some of the examples in this document show how you can install an HDInsight application using script action commands from PowerShell and the .NET SDK. For more information on HDInsight applications, see [Publish HDInsight applications into the Azure Marketplace](hdinsight-apps-publish-applications.md).
0 commit comments