@Ashnee Sharma Notice krb5-auth-dialog is optional Assuming you installed the KDC server yum -y install krb5-server krb5-libs krb5-auth-dialog Assuming you installed the KDC clients yum -y install krb5-auth-dialog krb5-workstation Your /etc/krb5.conf looks like below and copied to all the hosts in the cluster [logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log [libdefaults] default_realm = EXAMPLE.COM dns_lookup_realm = false dns_lookup_kdc = false ticket_lifetime = 24h renew_lifetime = 7d forwardable = true [realms] EXAMPLE.COM = { kdc = kdc.examplecom admin_server = kdc.examplecom } [domain_realm] .example.com = EXAMPLE.COM example.com = EXAMPLE.COM Your kdc.conf should resemble this [kdcdefaults] kdc_ports = 88 kdc_tcp_ports = 88 [realms] EXAMPLE.COM = { #master_key_type = aes256-cts acl_file = /var/kerberos/krb5kdc/kadm5.acl dict_file = /usr/share/dict/words admin_keytab = /var/kerberos/krb5kdc/kadm5.keytab supported_enctypes = aes256-cts:normal aes128-cts:normal des3-hmac-sha1:normal arcfour-hmac:normal des-hmac-sha1:normal des-cbc-md5:normal des-cbc-crc:normal } You kadm5.acl in /var/kerberos/krb5kdc as below */admin@EAMPLE.COM * Can you create an admin principal as suit # kadmin.local -q "addprinc admin/admin" Authenticating as principal admin/admin@EXAMPLE.COM with password. WARNING: no policy specified for admin/admin@EXAMPLE.COM; defaulting to no policy Enter password for principal "admin/admin@EXAMPLE.COM": Re-enter password for principal "admin/admin@EXAMPLE.COM": Principal "admin/admin@EXAMPLE.COM" created. This is the principal you should use for the Ambari Kerberos,make sure you started the appropriate daemons below Centos7/RHEL7 # systemctl start krb5kdc # systemctl start kadmin Centos6/RHEL6 # systemctl start krb5kdc # systemctl start kadmin All should be fine please let me know ... View more

@Jacqualin jasmin The simple answer is YES for MR This whole depends on the number of nodes in your cluster and the desired setup HA or NOT. Usually, there are Masternodes ,Datanodes and edge node (Clients Only) Masternode (if HA the recommended setup at least 3 nodes) - NAMENODE. - JOURNALNODE. - ZKFC. - NODEMANAGER. - HBASE_MASTER(Optional). - HISTORYSERVER. - APP_TIMELINE_SERVER. - RESOURCEMANAGER. - ZOOKEEPER_SERVER.(at least 2 ) - JOURNALNODE. - MYSQL_SERVER. - ZKFC. - HIVE_SERVER. - HIVE_METASTORE. - WEBHCAT_SERVER. - ZOOKEEPER_CLIENT. Datanode (As desired) - JOURNALNODE. - NODEMANAGER. - HBASE_REGIONSERVER(if Hbase installed). - ZOOKEEPER_CLIENT. - DATANODE Edgenode ( At least one) - YARN_CLIENT. - ZOOKEEPER_CLIENT. - RANGER_ADMIN. - RANGER_USERSYNC. - METRICS_MONITOR. - METRICS_COLLECTOR. - ZEPPELIN_MASTER. - INFRA_SOLR. - INFRA_SOLR_CLIENT. - HBASE_CLIENT. - HDFS_CLIENT. - TEZ_CLIENT. - YARN_CLIENT. - HIVE_CLIENT. - MAPREDUCE2_CLIENT In the above setup, some components are optional. See official Hortonworks document ... View more

@Pooja Kamle Do you have some error messages in hiveserver2.log? ... View more

@Charles Bradbury It should be frustrating, a simple diagnostic isn't easy just a quick look I saw some incompatibility in 2017-09-1516:58:19,901-StackFeatureVersionInfo:ClusterStack=2.5,ClusterCurrentVersion=None,CommandStack=None,CommandVersion=None->2.5 2017-09-1516:58:19,933-Using hadoop conf dir:/usr/hdp/current/hadoop-client/conf 2017-09-1516:58:19,953- checked_call['rpm -q --queryformat '%{version}-%{release}' hdp-select | sed -e 's/\.el[0-9]//g''] {'stderr': -1} 2017-09-1516:58:19,985- checked_call returned (0,'2.6.0.3-8','') There is a conflict between 2.5 and 2.6.0.3-8 can you validate your hdp.repo in /etc/yum.repo.d/* Make sure you have only the one you intend to install in this case I think 2.6 yum clean all yum repolist Please revert ... View more