@Sriram Can you check the document reference by @Harald Berghoff ... View more

@Bhushan Kandalkar When you start or restart Hue on a secure cluster, keys are generated at $HUE_HOME. If generated keystore files already exist in that location, the script does nothing. The script is located here: $HUE_HOME/bin/secure.sh, and it runs with a set of default parameters, which should not be changed. What is your current cacert path? ... View more

@Bhushan Kandalkar Here is a tip In the [[ssl]] section of the file hue.ini (under the beeswax section), set validate to true. [[ssl]] # SSL communication enabled for this server. # Path to certificate authority certificates. ## cacerts=/path/cert.pem # Choose whether Hue should validate certificates received from the server. validate=true On a secure cluster: Make sure that no custom authentication mechanism is turned on and configure the hive-site.xml with the following properties: <name>hive.server2.thrift.sasl.qop</name> <value>auth-conf</value> <description>Sasl QOP value; one of 'auth', 'auth-int' and 'auth-conf'</description> </property> To restart Hue To restart Hive Metastore To restart HiveServer2 ... View more

@Arshadullah Khan To use SSL for Hiveserver2, you will need to first enable SSL for Hiveserver2. If you have already done that then the connect string should look like below beeline -n abcd -u jdbc:hive2://xyz.abc.org:10001/default;ssl=true;sslTrustStore=/path/to/truststore.jks;trustStorePassword=Password Hope that helps ... View more

@Michael Bronson Yes I understand there should be some conflict in the config, that's the reason I want you to validate the above parameters. ... View more

@Michael Bronson What is the IP of the kafka02? Create directories Create data and log directories for ZooKeeper and Kafka. To simplify this process we can add the directories within the user home directory. In a production environment, we would use different locations, e.g. separate mount points or physical disks for data and log directories. $ mkdir -p /home/kafka/zookeeper/data $ mkdir -p /home/kafka/kafka/kafka-logs ZooKeeper configuration for embedded Share your zookeeper.properties. Set the value to point to the new ZooKeeper directory created above. dataDir=/home/kafka/zookeeper/data At the end of this file add all available ZooKeeper servers. server.1=kafka01:2888:3888 server.2=kafka02:2888:3888 server.3=kafka03:2888:3888 Each in your cluster nodes needs a unique server id. ZooKeeper looks up this information from the following file in my case: /home/kafka/zookeeper/data/myid. You will have to execute a command like this on each server - using a different value for each instance. For instance 1 on server kafka01 we use the value "1". $ echo "1" > /home/kafka/zookeeper/data/myid Kafka server.properties. Each Kafka cluster node needs a unique id. We have to find the broker.id property in the configuration files and change the id for each server. broker.id=1 Make sure you have a unique id for your all your brokers broker.id ie 1,2 ,3 Did you change the log directory location specified in the log.dirs parameter? log.dirs= Update the listeners and advertised.listeners properties with the current Kafka node hostname. listeners: the address/server name and protocol kafka is listening to (internal traffic between Kafka nodes) advertised.listener: the address/server name and protocol clients can use to connect to the Kafka cluster (external traffic). Only need to be specified if different from above setting. i.e listeners=PLAINTEXT://kafka01:9092 advertised.listeners=PLAINTEXT://kafka01:9092 Next step is to tell Kafka which ZooKeeper nodes can be used to connect to. zookeeper.connect=kafka01:2181,kafka02:2181,kafka03:2181 Hope that helps you resolve the reboot problem ... View more