Clusters Hub (VisualDoop)
OverView
Once the user is authenticated to Indexima, he gets access to a hub of indexima Clusters
A Visualdoop Administrator would be able to attach a cluster into this hub.
A simple user (ie not an admin) would only see a list
Administrate Clusters attachments & connections
User must be VisualDoop Admin user to perform the following actions
Attach a cluster
then fill up all the information mandatory to connect to an existing Indexima cluster
How to fill the connection attachment string?
| Definition | Valid value | |
|---|---|---|
| Name of the cluster, eg to distinguish several contexts or environments. | Any string that only contains letters & digits. | |
| The hostname of the load balancer or of the master node for the console to connect to the cluster. | A valid internet hostname. | |
The port of the load balancer or of the master node for the console to connect to the cluster. | An integer port number. Default value: 9999 Note: the console will interact with the core engine on the following resulting url: http(s)://<cluster_hostname>:<cluster_port> Note: see parameter webui.ssl.enable to enable ssl for interactions between core engine and console | |
| The secret key customised in galactica.conf, for console to interact with the cluster. | Any string that only contains letters & digits | |
| The hostname of the load balancer or of the master node for any sql client to connect to indexima. | A valid internet hostname Note: If Zookeeper is used on top of indexima, the hostname must be the concatenation of available nodes. The port number (Hive port) will be suffixed automatically if missing. Eg: master0.co.internal:2181,master1.co.internal:2181,master2.co.internal:2181,master3.co.internal:2181 | |
The port of the load balancer or of the master node for any sql client to connect to indexima. | An integer port number. Default value: 10000 | |
| The optional hive parameters to add to the jdbc url to connect to indexima (depending on hive customisation). | Any valid hive parameters. Note: If Indexima is installed within a kerberized cluster, hive parameters are required to provide the kerberos parameters. Eg: ;principal=indexima/ip-192.168.0.1.internal@INDEXIMA.COM Note: If Zookeeper is used to loadbalance Indexima, the zookeeper parameters must be added. Eg: ;serviceDiscoveryMode=zooKeeper; zooKeeperNamespace=<indexima_zookeeper_namespace> Note: The resulting url used by console to access core engine will be jdbc:hive2://<hive_hostname>:<hive_port>/<hive_parameters> |
Edit cluster link connection string
Click on the Edit button so you can modify the connection string
Create a connection to a cluster
