Member since
03-11-2021
4
Posts
0
Kudos Received
0
Solutions
07-02-2021
05:18 AM
Hi Srinivas, Thanks for the update. Could you please give the kudos,if the solution has worked ? Thanks, Asish
... View more
03-29-2021
06:43 PM
As you mentioned certain cli tools are marked not to be supported, for your requirement being the kafka-server-startup and shutdowns scripts. It is not guaranteed that the manual setup initializes the context of Kafka the same way, as Cloudera Manager would. While it may work for the restart but there are environment scripts and some other process management that Cloudera Manager does. Hence, when you restart using Cloudera Manager there would be uncertainties on the state of the process. As you said you have problems accessing the Cloudera Manager UI, you can also use the Cloudera Manager API for your requirement. https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cm_intro_api.html
... View more
03-19-2021
11:01 AM
If you keep seeing this, check in the bash profile on all nodes, if the umask is set to something else. It should be 0022.
... View more
03-16-2021
03:08 AM
Hello @Monds you can recover the lease on the file, running below command: #hdfs debug recoverLease -path <path-of-the-file> [-retries <retry-times>] This command will ask the NameNode to try to recover the lease for the file (successfully close the file if there are still healthy replicas) Ref: https://blog.cloudera.com/understanding-hdfs-recovery-processes-part-1/
... View more