When creating an EMR cluster, if you do not check Enable Public Network Access for Cluster Master Node, you cannot access the WebUIs of relevant components through the native WebUI access addresses on the component management page. This document describes how to view native component WebUIs in a cluster where the public network access to master node is not enabled.
You can use a browser to access a component's WebUI over the private network. Below are the links to native WebUIs of each component:
Component | Link |
---|---|
HDFS UI | http://{cluster private IP}:4008 |
YARN UI | http://{cluster private IP}:5004 |
HBASE UI | http://{cluster private IP}:6001 |
HIVE UI | http://{cluster private IP}:7003 |
HUE UI | http://{cluster private IP}:13000 |
RANGER UI | http://{cluster private IP}:6080 |
STROM UI | http://{cluster private IP}:15001 |
OOZIE UI | http://{cluster private IP}:12000 |
GANGLIA UI | http://{cluster private IP}:1800 |
PRESTO UI | http://{cluster private IP}:9000 |
ALLUXIO UI | http://{cluster private IP}:19999 |
You can bind an elastic public IP (EIP) to the master node by following the steps below to access component WebUIs from a browser over the public network:
2. Adjust the network bandwidth settings of the CVM instance to which the EIP will be bound and make sure that its bandwidth is not 0; otherwise, the node cannot be connected.
In the CVM instance list in the CVM Console, select More > Resource Adjustment > Adjust Network for the target instance.
Adjust the bandwidth upper limit to an appropriate value to ensure that the bandwidth of the CVM instance is greater than 0.
ping
or ssh
command to check whether the EIP has taken effect. Make sure that the inbound rules of the security group allow ICMP and port 22.Note:After an EIP is bound, the access addresses of native component WebUIs in the EMR Console will stay unchanged. If you need to change the addresses in the console, please submit a ticket for assistance.
Was this page helpful?