Member since
10-02-2017
116
Posts
3
Kudos Received
8
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
999 | 07-18-2020 12:04 PM | |
1727 | 09-11-2019 01:14 PM | |
2501 | 08-16-2019 08:17 AM | |
6348 | 08-15-2019 12:23 PM | |
4205 | 05-14-2019 08:48 AM |
01-19-2022
11:49 AM
@kevmac you and @Eric_B can find out about the actual target Log4j library version for Cloudera's suggested remediation by consulting the blog post Cloudera Response to CVE-2021-44228. The version of the Log4j library that the aforementioned remediation script is intended for is specified in the very first paragraph, sub-headed Summary.
... View more
01-19-2022
11:49 AM
@kevmac you and @Eric_B can find out about the actual target Log4j library version for Cloudera's suggested remediation by consulting the blog post Cloudera Response to CVE-2021-44228. The version of the Log4j library that the aforementioned remediation script is intended for is specified in the very first paragraph, sub-headed Summary.
... 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
07-18-2020
12:04 PM
Solved: The Altus Director web console provides a way to update an environment's provider credentials, but only after all clusters/deployments have been deleted. To update the credentials for existing deployment, I had to use director's API: /api/d6.2/environments/{name}/provider/credentials "Update provider credentials for a specific environment"
... View more
09-11-2019
01:14 PM
We updated our Packer image build to skip the CIS rule for more restrictive umask (referenced above), after which Hue successfully started during cluster firstrun.
... View more
08-16-2019
08:17 AM
We discovered that there were sporadic network issues in the tunnel between Azure and AWS ( our director instance is in AWS). Our assumption is that this was causing transient connection issues between director and Azure instances. Declaring issue solved for now as we no longer are experiencing it.
... View more
08-15-2019
12:23 PM
OK - so it seems that the yum repo for cloudera manager was defined / pinned to 6.2 in the cluster definition - so of course Director did what it was being asked to do. Updated to point to 6.3. repository: "https://archive.cloudera.com/cm6/6.3/redhat7/yum/" repositoryKeyUrl: "https://archive.cloudera.com/cm6/6.3/redhat7/yum/RPM-GPG-KEY-cloudera"
... View more
07-18-2019
09:03 AM
From experience Director will really lag as you scale higher up. We are at 5 environments with about 40 deployments spanning thousand of nodes. Make sure you go into application.properties and increase the amount of threads for tasks. That really makes a difference from what I've been seeing.
... View more
07-15-2019
09:50 AM
Thank you for the clarification. D.
... View more