Service Console: Instance Overview Page

The Instance Overview page displays overview information of a Oracle Big Data Cloud cluster.

Topics

What You Can Do from the Instance Overview Page

Use the Instance Overview page to perform tasks described in the following topics:

What You See in the Overview Section

Element	Description
	Menu that provides the following options to manage the cluster: Big Data Cloud Console — Open the Big Data Cloud Console. Start — Start all the virtual machines (VMs) hosting the nodes of the cluster. Stop — Stop all the virtual machines (VMs) hosting the nodes of the cluster. Restart — Restart all the virtual machines (VMs) hosting the nodes of the cluster. Scale Out — Add one or more nodes to this Cluster. Access Rules — Manage access rules that control network access to service components. (Does not apply to Oracle Cloud Infrastructure) SSH Access — Associate an SSH public key to the cluster. Add Tags or Manage Tags — Associate tags with the cluster. If any tags are already assigned, then the menu shows Manage Tags; otherwise, it shows Add Tags. View Activity — View activities for all cloud services in your identity domain.
	Displays instance details.
	Click to start all the virtual machines (VMs) hosting the nodes of this cluster.
	Click to stop all the virtual machines (VMs) hosting the nodes of this cluster.
	Click to restart all the virtual machines (VMs) hosting the nodes of this cluster.
	Click to add one or more nodes to this cluster.
	Click to display the health of this cluster.
Instance Overview	Displays overview information for the cluster.
	Click to refresh the page.
Nodes, OCPUs, Memory, and Storage	Summary of resources being used: Nodes — Total number of nodes for this cluster. OCPUs — Total number of Oracle CPUs allocated across all clusters. Memory — Total amount of compute node memory allocated across all clusters. Storage — Total amount of raw block storage allocated across all clusters.
Status	Status of the Oracle Big Data Cloud cluster.
User Name	Administrative user name. For clusters that use Basic authentication, the administrative user name and password are used to access the cluster console, REST APIs, and Apache Ambari. For clusters that use IDCS for authentication, the administrative user name and password are used only to access Ambari. Cluster access is managed through IDCS.
Compute Shape	The shape of all the nodes in the Oracle Big Data Cloud cluster.
Spark Thrift Server	The URL for JDBC connection to Thrift. There are two relevant service URLs, one for Spark Thrift Server and one for Hive Thrift Server. The URLs differ depending on whether you have a Basic authentication cluster or an IDCS-enabled cluster. For IDCS-enabled clusters, interactions are routed through the load balancing server instead of going directly to the cluster, and that difference is reflected in the URL. Basic authentication cluster Spark Thrift Server: jdbc:hive2://ip_address:1080/default;ssl=true;sslTrustStore=path_to_truststore;trustStorePassword=truststore_password?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice Hive Thrift Server: jdbc:hive2://ip_address:1080/default;ssl=true;sslTrustStore=path_to_truststore;trustStorePassword=truststore_password?hive.server2.transport.mode=http;hive.server2.thrift.http.path=hs2service Where: `ip_address` is the IP address of the desired endpoint `path_to_truststore` is the absolute path to the Java Trust Store that holds the certificate `truststore_password` is the password used with the trust store IDCS-enabled cluster Spark Thrift Server: jdbc:hive2://cluster_name-load_balancing_server_URI/default;ssl=true?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice Hive Thrift Server: jdbc:hive2://cluster_name-load_balancing_server_URI/default;ssl=true?hive.server2.transport.mode=http;hive.server2.thrift.http.path=hs2service Where: `cluster_name` is the name of the cluster `load_balancing_server_URI` is the URI assigned to the cluster by the load balancing service For more information about Thrift access, see About Accessing Thrift.
Version	Version of Oracle Big Data Cloud configured on the cluster.
Ambari Server Host	The IP address of the server hosting Ambari.
Deployment Profile	The deployment profile for the cluster.
Spark Version	The Spark version, 1.6 or 2.1.
Show more / Show less	(For IDCS-enabled clusters only) Click to display or hide the IDCS Application field. The IDCS Application field is listed only for IDCS-enabled clusters.
IDCS Application	(For IDCS-enabled clusters only) The Oracle Identity Cloud Service (IDCS) application ID for the cluster. Click the link to access the IDCS application. See Use Identity Cloud Service for Cluster Authentication.
(for Resources)	Displays resource information for this cluster.
Host Name	Name of an individual node in the Hadoop cluster.
Public IP	IP address of an individual node in the Hadoop cluster.
Instance	The kind of node within the Oracle Big Data Cloud cluster. A node within a cluster can be a: Master node Compute only slave node Compute and storage node
OCPUs	Total number of Oracle CPUs allocated for this machine.
Memory	Total amount of compute node memory allocated for this machine.
Storage	Total amount of storage allocated for this machine.
(for the resource)	Menu that provides the following options: For Compute Slave nodes: Remove Node— Remove the virtual machine (VM) hosting the node from the cluster. Start— Start the virtual machine (VM) hosting the node of the cluster. Stop— Stop the virtual machine (VM) hosting the node of the cluster. Restart— Restart the virtual machine (VM) hosting the node of the cluster. For Master nodes: Restart— Restart the virtual machine (VM) hosting the `MASTER` node of the cluster.
(for Associated Services)	Click to display information about services associated with the Oracle Big Data Cloud cluster.
(for Load Balancer)	(For IDCS-enabled clusters only) Click to display the cluster URL and other details.

What You See in the Administration Section

Element	Description
Available Patches	A list of patches you can apply to the cluster.
	Click to refresh the page.
(for each listed patch)	Menu that provides the following options for the patch: Precheck — Check whether the patch can be successfully applied to the cluster. See Check Patch Prerequisites. Patch — Apply the patch to the cluster. See Apply a Patch.
(for Patch and Rollback History)	Displays the patch and rollback history for the cluster.
Details of Last Patching Activity	Expand to see a description of the actions taken during the last patching operation.
Rollback	Click to roll back the last patching operation. See Roll Back a Patch or Failed Patch.