Using Big Data Studio

Big Data Studio runs on the second utility node of an HA (highly-available) cluster, or on the first (and only) utility node of a non-HA cluster. Before Big Data Studio can be accessed from a browser, an administrator must:

• Make the node available to incoming connections from users. The node's private IP address can be mapped to a public IP address. Alternatively, the cluster can be set up to use a bastion host or Oracle FastConnect. See Connecting to Cluster Nodes with Private IP Addresses.
• Open port 30000 on the node by configuring the ingress rules in the network security list. See Defining Security Rules.

The default admin login credentials for Big Data Studio are as follows:

• User name: datastudio

• Password: Apache Ambari or Cloudera Manager admin password. This is the cluster admin password that was specified when the cluster was created.

The admin creates additional users and their login credentials, and provides the login credentials to those users. See Creating and Deleting Users.

To access Big Data Studio directly from a browser:

1. Open a browser window.
2. Enter a URL in the following format:

   https://<node_ip_address>:30000

   For example:

   https://192.0.2.0:30000

3. Log in with your credentials.

You can also create a load balancer to provide a secure front end for accessing services, including Big Data Studio. See Connecting to Services on a Cluster Using Load Balancer.

To perform these actions, you must have access rights on the cluster through the operating system.

To change the default route:

1. Connect as opc user to the utility node where Big Data Studio resides (the second utility node of an HA (highly-available) cluster, or the first and only utility node of a non-HA cluster).
2. Change to root user:

   sudo su

3. As root, confirm that you have the issue by using route -n. The issue exists if ens3 is being used for the default route (ens3 is the interface that corresponds to the cluster subnet). For example:

   $ route -n
   Kernel IP routing table
   Destination Gateway Genmask Flags Metric Ref Use Iface
   0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 ens3

   In this example, 10.0.0.1 is the cluster subnet gateway.

4. Determine the gateway for your subnet by running route -n | grep ens5. The output will look something like this:

   10.200.0.0 0.0.0.0 255.255.128.0 U 0 0 0 ens5

   where the first string is the network (in this case, 10.200.0.0). The gateway is the network incremented by 1 (in this case, 10.200.0.1).

5. Add the new default route:

   route add default gw <your-subnet-gateway> ens5

   In the example above, <your-subnet-gateway> is 10.200.0.1, so the command would be:

   route add default gw 10.200.0.1 ens5

6. Remove the previous default route:

   route del default gw <cluster-subnet-gateway>

   In the example above, <cluster-subnet-gateway> is 10.0.0.1, so the command would be:

   route del default gw 10.0.0.1

7. Verify the new default route. You should see something like this:

   $ route -n
   Kernel IP routing table
   Destination Gateway Genmask Flags Metric Ref Use Iface
   0.0.0.0 10.200.0.1 0.0.0.0 UG 0 0 0 ens5

Each section is accessed from the icons on the left.