thanks Gangwar for your help.   I did reset the password following the instruction given in this link https://www.a2hosting.in/kb/developer-corner/mysql/reset-mysql-root-password   thanks again ... View more

@muslihuddin  I would encourage you to use the live doc version: https://docs.cloudera.com/runtime/7.2.1/security-ranger-authorization/topics/security-ranger-tag-service-add.html   However that's been fixed in recent releases, but not back-ported to 7.1.1 yet: https://docs.cloudera.com/cdp-private-cloud-base/7.1.4/security-ranger-authorization/security-ranger-authorization.pdf   Thanks for the feedback.  ... View more

@GangWar  Thank you for your reply. I confirmed I can manually upgrade the agent in each host , which is also written in installation manual as option 2. Upgrade the Agents using the Command Line. Just a little bit I have a curiosity of the reason not working with CM distributed method, but anyway I'm going forward steps.   Best regards, Tak568 ... View more

@atl-techdev Cloudera don’t support Oracle Database for Nifi Registry officially. Please check the matrix here:  https://docs.cloudera.com/cfm/2.0.4/support-matrix/topics/cfm-supported-databases.html ... View more

@Ananya_Misra  Namenode restart failed with below exception :   'org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /hadoop/hdfs/namenode is in an inconsistent state: previous fs state should not exist during upgrade. Finalize or rollback first.' This issue occurs because, during an upgrade, NameNode creates a different directory layout under NameNode directory, if this is stopped before Finalize upgrade, NameNode directory will go to an inconsistent state. NameNode will not be able to pick the directory with a different layout.   To resolve this issue start Namenode manually through command line with the -rollingUpgrade started option and proceed with the upgrade:   # su -l hdfs -c '/usr/hdp/current/hadoop-client/sbin/hadoop-daemon.sh --config /usr/hdp/current/hadoop-client/conf start namenode -rollingUpgrade started ... View more

'abort_procedure' is deprecated and not available. Seems now it needs to use 'hbck2 --bypass' in order to abort a procedure. We did not applied this because fortunately, an upgrade to CDH 6.3.3 for one cluster and a yarn patch on the other one, made a HBase restart necessary. That removed the peers on both clusters.   ... View more

@Cluster-CDP You can follow below Cloudera Recommendation about Role distribution as per number of nodes in the cluster. Though in your case this seems a best fit for me.  https://docs.cloudera.com/cloudera-manager/7.0.3/installation/topics/cdpdc-runtime-cluster-hosts-role-assignments.html   Master Hosts Utility Hosts Gateway Hosts Worker Hosts Master Host 1: NameNode YARN ResourceManager JobHistory Server ZooKeeper Kudu master Spark History Server One host for all Utility and Gateway roles: Secondary NameNode Cloudera Manager Cloudera Manager Management Service Hive Metastore HiveServer2 Impala Catalog Server Impala StateStore Hue Oozie Flume Gateway configuration HBase backup master Ranger Admin, Tagsync, Usersync servers Atlas server Solr server (CDP-INFRA-SOLR instance to support Atlas) Streams Messaging Manager Streams Replication Manager Service ZooKeeper 3 - 10 Worker Hosts: DataNode NodeManager Impalad Kudu tablet server ... View more