Member since
10-01-2018
802
Posts
144
Kudos Received
130
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 3552 | 04-15-2022 09:39 AM | |
| 2870 | 03-16-2022 06:22 AM | |
| 7506 | 03-02-2022 09:44 PM | |
| 3457 | 03-02-2022 08:40 PM | |
| 2365 | 01-05-2022 07:01 AM |
02-09-2021
05:06 AM
Thank you very much @GangWar I'll follow the instructions in shared docs.
... View more
02-08-2021
08:52 AM
Sorry, I forgot to post earlier. I was able to fix my own issue. I had to restart Ranger and Solr. One of the Solr instance failed on restart. But I was able to see Audit tab and other setting on Ranger. Thanks for looking into it.
... View more
02-08-2021
01:49 AM
@mdp Cloudera has changed the location of public binaries to implement the paywall. You can get more Information here on theses threads: https://community.cloudera.com/t5/Support-Questions/https-archive-cloudera-com-cm6-6-2-0-ubuntu1604-displaying/m-p/311114#M224468 https://community.cloudera.com/t5/Support-Questions/Paywall-also-for-CDH-6-3-x-and-open-source-availability/m-p/306682/highlight/true#M222959 To resolve the issue you have to generate the credentials to download the repo behind the Paywall and configure accordingly. To identify your authentication credentials using your license key file, complete the following steps: 1. From cloudera.com, log into the cloudera.com account associated with the CDP Private Cloud Base license and subscription agreement. 2. On the CDP Private Cloud Base Download page, click Download Now and scroll down to the Credential Generator. 3. In the Generate Credentials text box, copy and paste the text of the “PGP Signed Message” within your license key file and click Get Credentials. The credentials generator returns your username and password. https://docs.cloudera.com/HDPDocuments/Ambari-2.7.5.0/bk_ambari-installation/content/ch_obtaining-public-repos.html https://docs.cloudera.com/cdp-private-cloud/latest/release-guide/topics/cdpdc-cm-download-information.html
... View more
02-07-2021
08:51 AM
@marga Please follow this thread to get more info around this issue: https://community.cloudera.com/t5/Support-Questions/https-archive-cloudera-com-cm6-6-2-0-ubuntu1604-displaying/td-p/311035
... View more
02-07-2021
07:36 AM
hi if i need it for learning purpose then also i have to need a valid Subscription ? thanks
... View more
02-04-2021
06:51 AM
Hi @aakash_nand and @GangWar Thank you for your comment. Your advice is so helpful. https://cwiki.apache.org/confluence/display/RANGER/Presto+Plugin https://github.com/apache/ranger/blob/master/agents-common/src/main/resources/service-defs/ranger-servicedef-presto.json Now, I confirmed that Apache Ranger included in CDP 7.1.5 can display Presto on the Ranger administration screen using the Presto API. And, confirmed that Ranger can be configured on a per-account basis for Presto from the Ranger management configuration screen. Many thanks,
... View more
02-04-2021
12:50 AM
1 Kudo
@Ayyavaru Typically there is no external steps needed from CM side as CM only needs DB to be up so it depends on your plan honestly. However I would suggest you to take BACKUP of CM database for safe side [1] as well as plan downtime for this activity. You can use mysqldump to back up databases without having to shut them database down (see https://dev.mysql.com/doc/refman/5.7/en/mysqldump-sql-format.html). However, to ensure you get a good back, you should make sure there is no activity. i.e. you can get the back up by stopping the Cloudera manager server or any service for the database you are backing up. We strongly encourage that you consult your DBA or database vendor. After that you have to check the db.properties is rightly pointed to the database configured for CM. Hope this helps. [1]https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_ag_backup_dbs.html#concept_tyh_rmq_bl
... View more
02-03-2021
10:21 AM
@Pottie As per my you just have to install the krb packages on the new host rest will be fine and will be taken care by itself while adding host.
... View more
01-25-2021
09:36 AM
Thanks for the reply, @GangWar. The issue is sorted out now. As you said, the issue got fixed after checking the config.ini. The inter communications between the client and server were made to do over TLS, but we disabled the TLS/SSL in UI and for all agents. This was the main cause, as the heartbeat tried to get a response, but it didnt. Changing the configuration in Cloudera Manager -> Administration -> “Use TLS Encryption for Agents” should be unchecked, and restarting the Cloudera Manager fixed the issue.
... View more