Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.2.0
-
None
Description
Steps:
With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
Observe the configs of various services
Result:
Observed that the values of several properties showed up as blank and required (mostly security related). Here is the list:
HDFS:
- hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
- hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
- dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is present, which it is not in HDP 2.1)
YARN:
- yarn.authorization-provider (yarn-site, value is null, set to "org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if Ranger is present, which it is not in HDP 2.1)
Tez:
- tez.tez-ui.history-url.base (also tracked by
AMBARI-14389, tez-site, value is null, set to'{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol, server_host, server_port, latest_tez_jar_version)
by Stack Advisor)
HBase:
- hbase_principal_name (hbase-env, value is null, remove if not kerberized)
- hbase_user_keytab (hbase-env, value is null, remove if not kerberized)
ZK:
- zookeeper_keytab_path (zookeeper-env, value is null, remove if not kerberized)
- zookeeper_principal_name (zookeeper-env, value is null, remove if not kerberized)
Storm:
- nimbus_keytab (storm-env, value is null, remove if not kerberized)
- nimbus_principal_name (storm-env, value is null, remove if not kerberized)
- storm_keytab (storm-env, value is null, remove if not kerberized)
- storm_principal_name (storm-env, value is null, remove if not kerberized)
- storm_ui_keytab (storm-env, value is null, remove if not kerberized)
- storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
- nimbus.authorizer (storm-site, need help from Storm team on what to set this to since it depends on whether kerberos is enabled and Ranger is present)
Attached few screenshots
We may have more such issues for properties of services other than the ones with which the cluster was created at 2.1; so while fixing the issue, please ensure that all services are taken care of
Attachments
Attachments
Issue Links
- links to