Cloudera

I have encountered issues of the following scenario several times: A customer removes a host from a cluster managed by Cloudera Manger and adds the host to another cluster managed by Cloudera Manger. At this time, problems often occur. These problems are often caused by the old cluster files remaining on the host, and these old files cause the new Cloudera Manager to be unable to control the host normally. So I verified what files will be generated on a host after adding it to a CDP cluster managed by Cloudera Manager.\ In other words, after removing a host from Cloudera Manager, what files do we need to delete manually?

This article attempts to introduce how to forward the Kubernetes Service to the host node, and how to connect to the Cloudera CDSW database and modify the user's password.

This article records a troubleshooting about CDSW unable to start Session. The reason for the problem involved is that the remaining capacity of nodefs and imagefs used by Kubelet has reached the threshold of evicting the node, resulting in the node being labeled as NoSchedule taint by Kubernetes.