@geralt You need two steps process because of embedded DB.  1. Migrating from the Cloudera Manager Embedded PostgreSQL Database Server to an External PostgreSQL Database. 2. Then Migrating from the Cloudera Manager External PostgreSQL Database Server to a MySQL/Oracle Database Server   Hope this helps.    ... View more

@Marek I think it's definitely network issue now.  Node IP: "Public-IP-Address" not found in the host's network interfaces This message would indicate to me that the ip address of the host machine has changed or not at least above IP at network interface level of this host.  This thread is talked about the issue: https://github.com/kubernetes/kubernetes/issues/54337 The architecture which you are using is not supported, you might be able to hack thing using discussed in the thread: Using --hostname-override=external-ip arguments for kubelet  but not a long term solution. So you have to revise the network architecture is what I personally recommend to you as CDSW is little sensitive about this.  ... View more

@Marek No, that's a false alert, docker-registry shouldn't be accessible publicly. It's expected. The more worrisome part is this:  I0831 17:16:26.129073 10863 kubelet_node_status.go:279] Setting node annotation to enable volume controller attach/detach W0831 17:16:26.129340 10863 kubelet_node_status.go:481] Failed to set some node status fields: failed to validate nodeIP: Node IP: "Public-IP-Address" not found in the host's network interfaces I0831 17:16:26.131194 10863 kubelet_node_status.go:447] Recording NodeHasSufficientMemory event message for node cdsw-master-01.novalocal I0831 17:16:26.131229 10863 kubelet_node_status.go:447] Recording NodeHasNoDiskPressure event message for node cdsw-master-01.novalocal I0831 17:16:26.131239 10863 kubelet_node_status.go:447] Recording NodeHasSufficientPID event message for node cdsw-master-01.novalocal I0831 17:16:26.131255 10863 kubelet_node_status.go:72] Attempting to register node cdsw-master-01.novalocal E0831 17:16:26.131750 10863 kubelet_node_status.go:94] Unable to register node "cdsw-master-01.novalocal" with API server: Post https://Public-IP-Address:6443/api/v1/nodes: dial tcp Public-IP-Address:6443: connect: connection refused E0831 17:16:26.137202 10863 reflector.go:125] k8s.io/kubernetes/pkg/kubelet/kubelet.go:453: Failed to list *v1.Node: Get https://Public-IP-Address:6443/api/v1/nodes?fieldSelector=metadata.name%3Dcdsw-master-01.novalocal&limit=500&resourceVersion=0: dial tcp Public-IP-Address:6443: connect: connection refused E0831 17:16:26.138323 10863 reflector.go:125] k8s.io/kubernetes/pkg/kubelet/kubelet.go:444: Failed to list *v1.Service: Get https://Public-IP-Address:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp Public-IP-Address:6443: connect: connection refused E0831 17:16:26.139410 10863 reflector.go:125] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://Public-IP-Address:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dcdsw-master-01.novalocal&limit=500&resourceVersion=0: dial tcp Public-IP-Address:6443: connect: connection refused E0831 17:16:26.184663 10863 kubelet.go:2266] node "cdsw-master-01.novalocal" not found E0831 17:16:26.284919 10863 kubelet.go:2266] node "cdsw-master-01.novalocal" not found E0831 17:16:26.385174 10863 kubelet.go:2266] node "cdsw-master-01.novalocal" not found E0831 17:16:26.485392 10863 kubelet.go:2266] node "cdsw-master-01.novalocal" not found While if I see in my cluster with a grep of "Successfully registered node" there are positive outputs but not in yours. [DNroot@100.96 process]# rg "Successfully registered node" 2323-cdsw-CDSW_MASTER/logs/stderr.log 4919:I0824 07:47:48.639094 9038 kubelet_node_status.go:75] Successfully registered node host-10-17-xxx-xx 2213-cdsw-CDSW_MASTER/logs/stderr.log 4733:I0729 04:19:04.480413 26592 kubelet_node_status.go:75] Successfully registered node host-10-17-xxx-xx 2243-cdsw-CDSW_MASTER/logs/stderr.log.2 4629:I0729 04:25:25.114590 18483 kubelet_node_status.go:75] Successfully registered node host-10-17-xxx-xx 2182-cdsw-CDSW_MASTER/logs/stderr.log 5140:I0728 10:02:24.590379 11039 kubelet_node_status.go:75] Successfully registered node host-10-17-xxx-xx 2108-cdsw-CDSW_MASTER/logs/stderr.log 4761:I0707 03:34:20.010139 8360 kubelet_node_status.go:75] Successfully registered node host-10-17-xxx-xx 2123-cdsw-CDSW_MASTER/logs/stderr.log.1 4907:I0708 10:39:33.202393 6672 kubelet_node_status.go:75] Successfully registered node host-10-17-xxx-xx 2058-cdsw-CDSW_MASTER/logs/stderr.log 4747:I0703 04:18:25.271379 30286 kubelet_node_status.go:75] Successfully registered node host-10-17-xxx-xx So again I am back to the network issue 🙂  ... View more

@ipshubin Below should help.  1) Stop CDSW 2) Remove Spark gateway configuration from masternode. 3) Recreate the spark gateway configuration. 4) Start CDSW.  Also check if there is any softlink pointing to wrong directory on the hosts.  ... View more

@Prabhsimran Check if chronyd is also running on the server/hosts. You have to disable remove one of them means either you can use NTP or the chronyd. Then restart the clock service and see how it goes.  ... View more

@marcoboero I have heard some users was successfully done this. But the implementation can be tricky and the best way is to get in touch with Cloudera Sales Team for implementation. ... View more

@Mondi I guess yes. The encryption will take place in subdirectories as well. See the blog post. https://blog.cloudera.com/new-in-cdh-5-3-transparent-encryption-in-hdfs/   Though you can just give it a try my making any test file/dir.  ... View more

@buddelflinktier This is the compatibility matrix of HBase and info about HBCK tool.  https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/admin_hbase_hbck.html#concept_xhw_q4w_hr ... View more

@Marek Try to start CDSW in below manner and then see the logs for failed PODs if there is any.  1. Go to CM > CDSW > Stop (To stop CDSW first) 2. Go to CM > CDSW > Action > Run Prepare Node 3. Go to CM > CDSW > Instances i) Select Docker role Only from Master host and start. ii) Select Master Role from the Master host and start. iii) Then select Application Role from Master host and start. iv) Select Docker Role on Worker host and Start. v) At last select all Worker Roles from CDSW Hosts and start. ... View more