Accessing a Cluster
The following section describes how to access the various services in the cluster.
Navigating the Cloud Dashboard
To access the dashboard, you must log in to the cloud controller UI.
The Cloud Dashboard organizes clusters based on their status. Each cluster is represented by a tile.
The possible cluster status is:
- ACTIVE (currently running)
- IN PROGRESS (building, terminating or resizing/scaling)
- FAILED (failed to build)
You can access cluster details by clicking on the cluster's corresponding tile:
The cluster details page includes information about your cluster and all the nodes:
- Access cluster actions by clicking on CLUSTER ACTIONS.
- Access Ambari web UI, Ambari views, and other UIs by clicking on the icon. See Accessing the UIs.
- Copy complete SSH information for a specific node by clicking on the icon.
- If you enabled encryption for SSD storage attached to a specific node type, you will see the following icon .
The Cluster Details page includes the following section tabs:
|HARDWARE||Includes information about your cluster nodes: instance names, instance IDs (with links to the EC2 console), public IPs, and SSH connection information (with a copy option).|
|TAGS||Lists user-defined tags, in the same order as you added them.|
|NETWORK||Includes VPC and subnet IDs (with links to the VPC dashboard), remote access CIDR IP, and protected gateway access settings.|
|RECIPES||Lists pre-install and post-install node recipes (with a copy option).|
|ADVANCED||Lists Hive and Druid metastores, instance role setting for granting S3 access, and custom properties.|
|AUTO SCALING||Allows you to view and manage (add, delete, configure) current auto scaling policies and settings.|
The EVENT HISTORY tab shows you events logged for the cluster, with the most recent event at the top. For example, after your cluster has been created, the following messages will be written to the log:
2017-03-15 12:18:26 Success Ambari cluster built; Ambari ip:126.96.36.199 2017-03-15 12:14:06 Success Building Ambari cluster; Ambari ip:188.8.131.52 2017-03-15 12:09:15 Success Starting Ambari cluster services 2017-03-15 12:09:15 Success Setting up infrastructure metadata 2017-03-15 12:08:47 Success Bootstrapping infrastructure cluster 2017-03-15 12:08:47 Success Infrastructure successfully provisioned 2017-03-15 12:07:15 Success Infrastructure metadata collection finished 2017-03-15 12:07:14 Success Infrastructure creation took 173 seconds 2017-03-15 12:04:20 Success Creating infrastructure
Accessing a Cluster via SSH
If you plan to access the cluster via the command line clients, SSH into the master node instance in the cluster.
You can copy the full SSH statement from your Cluster Details page > HARDWARE section > SSH Connection column by clicking on the icon next to the master node:
Accessing Cluster Resources
For your convenience, you can access the Ambari web UI and other cluster components through a protected gateway:
From the cloud controller dashboard, by clicking on CLUSTER UIs:
From Cluster Details page, by expanding the Ambari and Cluster Components dropdown menus:
The availability of UIs and their corresponding links depends on the Protected Gateway Access settings that you chose when creating your cluster:
- The Ambari links are created by default, because the Protected Gateway Access to Ambari and Zeppelin Web UIs option is preselected by default when you create a cluster. If you uncheck this option, the links will not be created and you will be unable to access the Ambari web UI.
- The Cluster Components links are not created by default, and are only available when you check the Protected Gateway Access Cluster Components (NN, RM, JHS, SHS) option when creating a cluster.
|Ambari||Ambari Web UI and the Hive, Files and Tez views.|
|Zeppelin UI||Zeppelin Web UI (if your cluster configuration included Zeppelin).|
|Cluster Components||NameNode, ResourceManager, MapReduce JobHistoryServer and Spark History Server.|
Accessing the UIs
Access to cluster resources and UIs is via the protected gateway. By default, the gateway has been configured with a self-signed certificate to be accessed via HTTPS. The first time you access the server, your browser will attempt to confirm that the SSL Certificate is valid. Since we are automatically generating a self-signed certificate, your browser will warn you about an Untrusted Connection and ask you to confirm a Security Exception. Depending on your browser, perform the steps below to proceed.
See Using Your Own SSL Certificate for more information on replacing the self-signed certificate with your own trusted certificate.
|Firefox||Click Advanced > Click Add Exception... > Click Confirm Security Exception|
|Chrome||Click Advanced > Click Proceed...|
If you are accessing cluster component UIs, you will be prompted to authenticate. Use the Cluster User credentials that you created when creating your cluster:
You can access the Ambari web UI once the create cluster process is complete. If you try to access Ambari while the cluster is being created, you will get a 502 Bad Gateway error.
Setting Configuration Properties
You can set configuration parameters by specifying custom properties when launching your cluster.
If you want to edit configuration configuration parameters when the cluster is already running, you can do this using Ambari web UI. Refer to Configuring Services documentation in the Ambari User Guide.
You can also set configuration parameters using Ambari API.