@Sree Kupp If the NameNode host has hardware problems and you need to move the NameNode to another host, you can do so as follows: If the host to which you want to move the NameNode is not in the cluster, follow the instructions in Adding a Host to the Cluster to add the host. Stop all cluster services. Make a backup of the dfs.name.dir directories on the existing NameNode host. Make sure you back up the fsimage and edits files. They should be the same across all of the directories specified by the dfs.name.dir property. Copy the files you backed up from dfs.name.dir directories on the old NameNode host to the host where you want to run the NameNode. Go to the HDFS service. Click the Instances tab. Select the checkbox next to the NameNode role instance and then click the Delete button. Click Delete again to confirm. In the Review configuration changes page that appears, click Skip. Click Add to add a NameNode role instance. Select the host where you want to run the NameNode and then click Continue. Specify the location of the dfs.name.dir directories where you copied the data on the new host, and then click Accept Changes. Start cluster services. After the HDFS service has started, Cloudera Manager distributes the new configuration files to the DataNodes, which will be configured with the IP address of the new NameNode host. Go to the HDFS service. The NameNode, Secondary NameNode, and DataNode roles should each show a process state of Started, and the HDFS service should show a status of Good. You can't disturb between multiple node unless you want to store HDFS metadata in multiple location which will be same. ... View more

@suresh krish When you see the environmental variables in your spark UI you can see that particular job will be using below property serialization. If you can't see in cluster configuration, that mean user is invoking at the runtime of the job. <code>spark.serializer org.apache.spark.serializer.KryoSerializer Secondly spark.kryoserializer.buffer.max is built inside that with default value 64m. If required you can increase that value at the runtime. Even we can all the KryoSerialization values at the cluster level but that's not good practice without knowing proper use case. Hope this helps you. ... View more

@Deepak Nayak We can submit the spark jobs on remote cluster using the livy server using Rest calls. Below are the couple of links for examples: https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-apache-spark-livy-rest-interface https://github.com/cloudera/livy Hope this helps you. ... View more

@arjun more Are you able to sync groups similar like users? If not, please check below parameter with your LDAP team and add them as per their request: authentication.ldap.groupObjectClass [LDAP Object Class] The object class that is used for groups. Example: groupOfUniqueNames authentication.ldap.groupMembershipAttr [LDAP attribute] The attribute for group membership. Example: uniqueMember authentication.ldap.groupNamingAttr [LDAP attribute] The attribute for group name. Checking the ambari-server logs would help you in getting the error message. Hope this helps you. ... View more