Hive - Zookeeper Configuration

in addition to the databases previously mentioned, kron pam sql proxy can be configured to work with zookeeper databases this section outlines the steps required to integrate zookeeper databases into kron pam, including specific property configurations and host file modifications modifying the /etc/hosts file for zookeeper nodes to ensure that kron pam can resolve the hostnames of the zookeeper nodes, you need to update the /etc/hosts file on the kron pam machine access the kron pam server via ssh open the /etc/hosts file with a text editor (e g , vi /etc/hosts) add the following entries to map the zookeeper node ip addresses to their hostnames 172 191 43 234 hive masternode 01 172 173 226 15 hive datanode 02 52 170 134 60 hive datanode 03 40 114 55 184 hive metanode 04 to connect hive nodes user needs to upload the hive jdbc files into pam/gui/lib in your pam machine adding zookeeper as a device firstly, add the zookeeper database to kron pam as a device navigate to devices > inventory click the add select add device in the information section, enter all the information below then enter the sql proxy bind port (last section in ‘add device’) ip address it is the equivalent name of the ip address in the etc/hosts file device name a unique name for the hive node it is not required port the port number used by hive (if not specified, the default port is used) access protocol choose hive element type choose hive enter sql proxy bind port (in this case 1019) save in the information section, enter the required details ip address the ip address of the zookeeper database device name a unique name for the zookeeper device port the port number used by zookeeper access protocol select the protocol appropriate for the zookeeper element type choose database enter sql proxy bind port (in this case 1022) save then return to the hive node that you need to connect; (in this case, this will be our first defined hive db named hive datanode 3 ) zookeeper requires specific properties to be set in kron pam to enable proper communication and metadata management click the edit device then click the edit database button enter your information on this screen in the device's properties section, add the following parameters (the properties that were not written with bold are examples) external metastore vendor mysql external metastore host 40 114 55 184 external metastore port 3306 external metastore username hiveusr external metastore name metastore db external metastore password enc hivepassword (ensure the password is encrypted) metadata type external after these configurations user should be defined as user groups, device groups, and policy groups like any other sql proxy in this case, this document assumes you have knowledge if not, you can check out docid\ y4fehe v0uwcbqtfxybvm reminder knowledge connecting to zookeeper via kron pam sql proxy users can connect to the zookeeper database through the kron pam sql proxy using an sql client open an sql client (e g , dbeaver, datagrip) create a new connection and select the appropriate database type enter the following connection details host the ip address of the kron pam server please look at below example of the url below that contains the host port and any etc ) jdbc\ hive2 //10 20 42 159 1022/newdb;servicediscoverymode=zookeeper;zookeepernamespace=hiveserver2; port the sql proxy port assigned to the zookeeper device in kron pam username the username configured in kron pam (must match the database username) password the corresponding password database/service name the name of the zookeeper database as defined in kron pam test the connection to ensure that it is successful it is recommended to use the hive zookeeper connection with version 23 1 2 of dbeaver