Big Data Cloud Console: Settings Page
The Big Data Cloud Console: Settings page displays information for managing resource queues configurations, notebook server restart, and interpreter settings for the Big Data Cloud cluster.
Topics
What You Can Do from the Big Data Cloud Console: Settings Page
Use the Settings page to perform tasks described in the following topics:
What You See in the Navigation Area
Element | Description |
---|---|
User menu providing access to the API Catalog for Big Data Cloud, Help for this page, and About information with details about the console. |
|
Overview |
Click to go to the Overview page. |
Jobs |
Click to go to the Jobs page. |
Notebook |
Click to go to the Notebook page. |
Data Stores |
Click to go to the Data Stores page. |
Status |
Click to see information about components and services running on Oracle Big Data Cloud clusters and nodes and their associated state. |
What You See in the Queues Region
Element | Description |
---|---|
Click to create a new Queue. |
|
Preemption |
Displays if Preemption is enabled or disabled for queues.
|
Queue Name |
The name used to identify the resource queue. |
Capacity (%) |
The guaranteed capacity of each queue which specifies the percentage of cluster resources that are available for applications submitted to the queue. |
Max Capacity (%) |
The maximum capacity of the queue. Max Capacity is automatically sets to 100% when preemption is enabled. Otherwise it is the same as Capacity. |
Total Queues Capacity |
The total capacity of all queues put together. |
What You See in the Credentials Region
Element | Description |
---|---|
Cloud Storage |
Allows you to reset the Oracle Cloud Infrastructure Object Storage Classic password associated with the cluster. This password is associated with the account used during provisioning of the cluster. It should only be changed if the Oracle Cloud Infrastructure Object Storage Classic password has been changed outside of the Big Data Cloud service.
|
System Credentials |
System Credentials are secrets required by the platform (including the Oracle Cloud Infrastructure Object Storage Classic password) which are updated through the system credential User Interface and/or the REST API. Any credentials held within the system credential store can be updated, but they cannot be deleted. Credentials stored in the System and User Credential store are accessible to applications during runtime through the Apache |
User Credentials |
For a cluster, User Credentials allows you to store a user or application specific credentials in the credential store.
|
What You See in the JDBC URLs Region
Element | Description |
---|---|
Spark Thrift URL |
URL for the Spark Thrift Server. The URLs differ depending on whether a cluster uses Basic authentication or uses IDCS for authentication. For information about cluster authentication, see Use Identity Cloud Service for Cluster Authentication. Basic authentication cluster 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 Where:
IDCS-enabled cluster jdbc:hive2://cluster_name-load_balancing_server_URI/default;ssl=true?hive.server2.transport.mode=http;hive.server2.thrift.http.path=cliservice Where:
For more information about Thrift access, see About Accessing Thrift. |
Hive Thrift URL |
URL for the Hive Thrift Server. The URL is different depending on whether you have a Basic authentication cluster or an IDCS-enabled cluster. Basic authentication cluster 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:
IDCS-enabled cluster jdbc:hive2://cluster_name-load_balancing_server_URI/default;ssl=true?hive.server2.transport.mode=http;hive.server2.thrift.http.path=hs2service Where:
For more information about Thrift access, see About Accessing Thrift. |
What You See in the Notebook Region
Element | Description |
---|---|
Click to restart the notebook server when the data is cached. |
Apart from restarting Notebooks, you can also manage interpreter settings for Notebooks from this region.