RAD
ProductsLanguageHome
  • Rapid Alluxio Deployer (beta)
  • Get started
    • Sign up
    • Deploy
      • Create a Managed Access
      • Create a cluster
      • View cluster details
      • Delete cluster
    • Demos
      • FIO
    • Running jobs
      • Alluxio free cache
      • Fio benchmark
  • Architecture and Security
    • Split plane architecture
Powered by GitBook
On this page
  • View cluster details
  • View cluster info
  • Metrics dashboard
  • SSH access to instances
  • Alluxio installation directory and user
  1. Get started
  2. Deploy

View cluster details

Last updated 7 months ago

View cluster details

After the cluster has started, it will display the cluster parameters and details about its provisioned resources.

The resource tag is a unique id to help identify the resources provisioned for this cluster. All resources, such as VPCs and EC2 instances, are tagged with the key ResourceTag and the unique id as the value.

View cluster info

The cluster info section prints a JSON text describing the additional EC2 instances launched for the cluster. The exact layout may differ depending on the cluster type.

Instances are grouped as masters, workers, or clients; different processes are deployed on each. One or more instances could be deployed for each group. Each instance lists its private IP and its public DNS if the instance is publicly accessible.

The static mounts section describes the storages that are mounted to the Alluxio namespace, mapping the mount point to the UFS URL.

Metrics dashboard

Metrics from the cluster are reported and displayed on the dashboard at the bottom of the page, in the form of a Grafana dashboard.

SSH access to instances

This section is only applicable if a SSH key was provided when creating the corresponding managed access entry.

Instances with a public DNS, shown in the cluster info view, allow SSH access using the corresponding private key matching the public key provided when creating the Managed Access. Each cluster's agent node will always have a public DNS. It serves as a bastion host to the cluster as it has SSH access to every other node in the cluster.

ssh -i /path/to/private/key ec2-user@instancePublicDns

Instances with only a private IP are only accessible within the VPC. To SSH into these instances, first SSH into the agent node, then from within the agent, SSH into the destination instance via its private IP.

# from your terminal with your private key
ssh -i /path/to/private/key ec2-user@agentPublicDns

# from within the agent node, using its default SSH private key
ssh ec2-user@privateIp

Alluxio installation directory and user

The Alluxio installation directory is located at /opt/alluxio on any node running an Alluxio process.

Note that the owner of the directory as well as the owner of the running Alluxio processes is the alluxio user, which is different than the ec2-user user used to SSH into the EC2 instance. It is recommended to switch to the alluxio user before executing commands related to Alluxio by running:

sudo su alluxio

After switching users, check the running java processes by running:

jps

Check the Alluxio version by running:

cd /opt/alluxio
bin/alluxio info version

A cluster will always be deployed with an agent node that is publicly accessible via its public DNS. It is possible to SSH into the instance if a SSH key was provided when creating the managed access; see for information.

SSH access to instances
Metrics dashboard