@hanumanth  It seems you are using other services also with embedded DB than Cloudera Manager? I see hive user also in the output. Embedded DB is only for trial poc use cases and not designed to scale. You should consider moving to external databases. https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/installation/topics/cdpdc-installing-trial-cluster.html Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.   ... View more

@sanjaysubs glad to know manual install worked. The fact that install was successful in CM node, means there was probably issue with missing allkeys.asc. This file should be present in the repository that you configure in the add host wizard on CM UI. This is required by the install wizard in the nodeconfigurator process for installation of other CM agent nodes. ... View more

This issue would be fixed in our upcoming release. You can check for a hotfix.   You can try adding the below workaround as well to see if performance improves. a. On the target cluster, Go to CM-> Hive-> Configuration b. Add "HIVE_REPL_STATS_ENGINE=hive" to the "Hive Replication Environment Advanced Configuration Snippet (Safety Valve)" configuration .   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

you should check the container logs for the one mentioned in the snapshots above for more details. Generally caused due to resource crunch. You can consider increasing the below yarn configs as well. yarn.nodemanager.resource.memory-mb yarn.nodemanager.resource.cpu-vcores   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@frank_albers @PNW supervisor has a listener process which keeps monitoring the CDH processes. For any service with auto restart configured if faces an unexpected exit , supervisord will restart the process. Agent looks for unexpected exits in the notifications it receives via the  supervisor listener and forwards relevant event info to the associated  role's monitor to update its unexpected exit state. A normal agent restart does not affect supervisord process, it continues to be running and managing CDH processes. A hard stop/restart on agent will affect supervisord and in turn kill all managed CDH processes.   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.     ... View more

@sanjaysubs You should be able to track operations and relevant logs under details page if you retry the operation. Also check CM server logs before the message:  Failed to complete installation  that should give more details. Make sure your CM repo has allkeys.asc file. If not add it from the cloudera repository link.   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@snm1523    1. This is a functionality to be provided by the OS vendor since package installations use yum which is not Cloudera managed. 2. No we don't have another way. Ideally for both these security specific use cases, you should create temporary /local repositories only where authentication is not required.   https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/upgrade/topics/cm_ig_create_local_package_repo.html     Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@PDDF_VIGNESH  I hope you have connected to the port configured for your cluster.Does the URL return successful response on browser? The responses need to be checked only during the time of issue.   The JMX is generated by datanode. Not getting a response means there are either issues with datanode or any network issues with the coomunication.       ... View more

@PDDF_VIGNESH    See if you are able to get successful response from the agent to the host reported in the logs below: http://datanode02.hadoop:1006/jmx Few checks: 1. curl http://datanode02.hadoop:1006/jmx 2. telnet datanode02.hadoop:1006   If this is successful, restart the agent. If there is issue with response, you need to review DN logs for issues/workarounds suggested previously.   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.   ... View more

@Juris     The default filter value of 7 days is hardcoded in Hue.  You can find this set in your cluster hosts /usr/lib/hue/apps/jobbrowser/src/jobbrowser/templates/job_browser.mako [default file] as shown below. As a workaround this file can be edited across all hosts followed by Hue restart but changes would persist for all users. We generally don't recommend to edit the install files but just providing you with the information here.   self.timeValueFilter  = ko.observable  (7).extend({ throttle: 500 }); self.timeUnitFilter   = ko.observable  ('days').extend({ throttle: 500 });   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@Jua    Cloudera expects HA solutions for RDBMS to be transparent to Cloudera software, and therefore are not supported and debugged by Cloudera.   Having said that you can try to modify the /etc/cloudera-scm-server/db.properties with the URL in below format and test it out. com.cloudera.cmf.db.type=oracle com.cloudera.cmf.orm.hibernate.connection.driver_class=oracle.jdbc.driver.OracleDriver com.cloudera.cmf.orm.hibernate.connection.url=jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=off)(FAILOVER=on) / (CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS=(PROTOCOL=TCP)(HOST=hostname1)(PORT=1521)) / (ADDRESS=(PROTOCOL=TCP)(HOST=hostname2)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<Oracle-SID>))) com.cloudera.cmf.orm.hibernate.connection.username=<CM-Oracle-user> com.cloudera.cmf.orm.hibernate.connection.password=<password>   I suggest to check with your DB vendor to validate the jdbc URL if this still fails.   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@Zhaojie    The errors to focus here are the below ones which are causing unknown health alerts. This is being caused because CM agent is not able to connect to Host Monitor.   Please ensure the hosts generating the alerts have space available and are not overloaded in terms of COU and memory. You can also try to hard restart the CM agents if this is feasible option since hard restart will stop the services running on the host and clear any thread deadlocks in cluster services.   The health test result for HOST_SCM_HEALTH has become bad: This host is in contact with the Cloudera Manager Server. This host is not in contact with the Host Monitor. The health test result for HOST_AGENT_LOG_DIRECTORY_FREE_SPACE has become unknown: Not enough data to test: Test of whether the Cloudera Manager Agent's log directory has enough free space.   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.   ... View more

@akshay0103    Please check the Hue.ini content under field  [useradmin] if there are any non default permissions being used? Are you adding the user using create home directory permissions?   ... View more

@Mondi    Cloudera provides two implementations of the Hadoop KMS. Refer below document for more details. https://docs.cloudera.com/documentation/enterprise/latest/topics/cdh_sg_kms.html You need to install Key Trustee KMS only when using KTS as backing keystore instead of the file-based Java KeyStore (JKS) used by the default Hadoop KMS.   There should be a separate cluster for keytrustee server. This would be mentioned as one of the steps when you enable HDFS encryption via the wizard.   Refer below document https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/sg_hdfs_encryption_wizard.html#concept_n2p_5vq_vt   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@Mondi    You do not need to install Cloudera Navigator for KMS and KTS. Refer : https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/encryption_prereqs.html#concept_g23_454_y5__section_n4w_b5v_ls   Please refer below documents for encrypting data at rest requirement and installing KMS and KTS.  You must install Key Trustee Server before installing and using Key Trustee KMS.   https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/encryption_planning.html#concept_c4m_knq_w5 https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/key_trustee_install.html#xd_583c10bfdbd326ba-590cb1d1-149e9ca9886--7b84 https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cm_ig_install_keytrustee.html#xd_583c10bfdbd326ba-590cb1d1-149e9ca9886--7860   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@Mondi  Please refer below document which explains steps to configure jar for UDFs.  You can configure the cluster in one of several ways to find the JAR containing your UDF code, and then you register the UDF in Hive. https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_mc_hive_udf.html#xd_583c10bfdbd326ba--43d5fd93-1410993f8c2--7ea3   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@rmr1989    Ideally, for a missing mounts in the cluster you would automatically get alerts for services if any hadoop service directories cannot be accessed which are mapped to the mountpoint. They can be generic though like "no such file or directory" or "file not found" errors.   If you are looking for specific mountpoint availability, you should consider using script to scan for mountpoints in the cluster hosts and can send email alerts using SMTP from the host instead of Cloudera Manager.   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.           ... View more

@rmr1989    You can edit the expression manually to include the NOT operator. Check the below example which uses NOT operator for a trigger. A trigger expression takes the form: IF (CONDITIONS) DO HEALTH_ACTION   A condition is any valid tsquery statement with below syntax.  SELECT [metric expression]WHERE [predicate]   Mount point is an attribute which can be used in filter conditions but not metric expression. Hence, I believe it would not be possible to create a trigger on mount point scans.   Refer below document which lists the supported metrics: https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_metrics.html#xd_583c10bfdbd326ba--7f25092b-13fba2465e5--7e52   Example:   IF (SELECT total_xceivers_across_datanodes WHERE serviceName=$SERVICENAME AND last(total_xceivers_across_datanodes) != 0 AND entityName = "HDFS-1:ns1" AND category = "SERVICE") DO health:concerning   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@pdev    Yes, BDR  is supported between different CDH versions.   Refer below links for more details https://docs.cloudera.com/documentation/enterprise/5-14-x/topics/cm_bdr_replication_intro.html#concept_rt2_1wt_bx   https://docs.cloudera.com/documentation/enterprise/6/release-notes/topics/rg_pcm_bdr.html#bdr   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@Prav    You can leverage CM API to track parcel distribution status: /api/v19/clusters/{clusterName}/parcels - This can be used to note the parcel name and version the cluster has access to   /api/v19/clusters/{clusterName}/parcels/products/{product}/versions/{version} - This can be used to track the parcel distribution status   Refer below link for more details http://cloudera.github.io/cm_api/apidocs/v19/path__clusters_-clusterName-_parcels_products_-product-_versions_-version-.html   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more