Member since
12-16-2019
10
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
427 | 05-18-2020 01:02 AM |
12-28-2020
06:25 AM
@geralt There is no easy way like that but the way you suggested could work the CM and the other services needs the databases up and connected without interference.
... View more
09-09-2020
02:08 PM
@geralt Oozie workflows etc. is not the part of CM database. Hue has it's own Database so for migration those stuffs you will be needing to Migrate Hue Database.
... View more
05-18-2020
01:02 AM
I'll answer myself since I found out what the problem was. Since I "inherited" this cluster I am not aware of all the things that have been done on it. I've found out that on the node that hosts the Cloudera Manager and some of the other the JCE was manually installed. So what I did was to manually install JCE on the other nodes that were missing the library (it's a very simple procedure, you just have to copy two jars in the java home). Then the Kerberos installation was smooth sailing like the other times I did it. I think that maybe the CM should have a way to indicate a situation like this and not hang forever leaving the user completely unaware of what is happening. In my case I was lucky that I could ssh into the nodes and investigate about the issue.
... View more
04-16-2020
04:49 PM
Hi @geralt ,
Thanks for reaching out to Cloudera community.
SAML is theoretically a standard so it might work with OAM. However, we have not tested this in house neither we have supported it. This matches your findings from reading the public documentation.
Sorry can not give you more assistance on this one. Good luck!
Li
... View more
01-09-2020
12:25 AM
Hello and happy new year! I'm sorry for the delay of my response, but I somehow managed to solve the issue. The fact was that I was trying to import the cluster template on a cluster that was already "initialized". What I think it happened is that during my tests with the cluster template I wrote a malformed json file (which brought to some errors during the installation) but the cluster template install command still managed to create an empty cluster. When I tried again the procedure with the correct cluster template json I didn't think about deleting the cluster and this caused the issue I presented in the post. When I deleted from scratch everything and tried again the procedure it worked. By the way I followed this documentation https://docs.cloudera.com/documentation/enterprise/latest/topics/install_cluster_template.html
... View more