@Michael Young Thanks!! article is very useful. ... View more

@Jay SenSharma I was going through below mentioned link if i need to setup CA signed certificate. I am going to mention list of steps to be performed on 3 node cluster(excluding edge node). Please validate keytool -genkey -keyalg RSA -alias c6401 -keystore /tmp/keystore.jks -storepass bigdata -validity 360-keysize 2048 (To be generated for each Node(master, slave1 and slave2)) keytool -certreq -alias c6401 -keyalg RSA -file /tmp/c6401.csr -keystore /tmp/keystore.jks -storepass bigdata( csr file to be generated for each node keystore.jks file) Nowget the singed cert from CA - file name is/tmp/c6401.crt( How to get this certificate for each node/or single node from CA)? Import the root cert to JKS first.(Ignoreif it already present) keytool -import-alias root -file /tmp/ca.crt -keystore /tmp/keystore.jks (How to get root cert)? Repeat step4 for intermediate cert if there is any.? Import signed cert into JKS. keytool -import-alias c6401 -file /tmp/c6401.crt -keystore /tmp/keystore.jks -storepass bigdata ( to be done for each node)? keytool -import-alias root -file /tmp/ca.crt -keystore /tmp/truststore.jks -storepass bigdata (To be done for each node)? Kindly let me know if this is correct approach? Or is there any other link for multi node? Thanks for great help!! https://community.hortonworks.com/articles/52875/enable-https-for-hdfs.html ... View more

@rahul gulati I thought I have covered all the steps in the article. The only different for self signed and CA signed is STEP1 - so both mentioned there. for CA signed cert CA signing would provide you their root CA so that it can trust all their certs ... View more

@Jay SenSharma Following the link below i have added all the resp. properties in custom core-site.xml(Ambari) But no success. http://docs.hortonworks.com/HDPDocuments/Ambari-2.2.2.0/bk_ambari_views_guide/content/_configuring_your_cluster_for_files_view.html i have added 4 more properties named as hadoop.proxyuser.root.groups=* hadoop.proxyuser.root.hosts=* hadoop.proxyuser.admin.groups=* hadoop.proxyuser.admin.hosts=* ... View more

I was able to deploy the cluster. Thanks!! ... View more

@rahul gulati Are you sure that when you are running the following command on those hosts individually then you are getting the correct FQDN? hostname -f - Ambari agent sends registration request to ambari-server every time when agent is restarted. In the registration request it sends the FQDN information of it's own as well. Agent uses the following approach to findout the FQDN using python. So please check if all your hosts are returning correct hostname python -c "import socket; print socket.getfqdn()" . Also in local system it might get using which is not actually FQDN as above. So local agent might behave bit differently then remote. python -c "import socket; print socket.gethostname()" ... View more

@Attila Kanto Just a quick thought.My cloudbreak instance is running on old VM. So if i go by your saying and delete old VM completely then will my new Cluster(on new VM's) still be running? As i would not be able to access cloudbreak UI after deletion of old VM's. Thanks Rahul ... View more

@rahul gulati Could you please accept the answer if it is answered your question? ... View more

@rahul gulati Earlier I observed that this similar exception occurred at the time of launching of Oozie workflow. Can you try to set following memory related parameter in Oozie workflow.xml with some higher value like 1024mb so that workflow launches successfully. For e.g: <property> <name>oozie.launcher.mapred.map.child.java.opts</name> <value>-Xmx1024m</value> </property> See if this helps you. ... View more

@rahul gulati Unfortunately cloudbreak currently does not support deploying the cluster on existing machines. The only way is to provision clusters if you deploy the whole cluster end to end. Delete those vm's and please start a new cluster. Br, R ... View more