While loading fsimage why the permissions=nifi:hdfs:rwx in-place of hdfs:hadoop Encountered exception on operation MkdirOp ... View more

bc3dcd485adfa1c339eab38f1516c6c5 >> These alpha numeric related to tablet from kudu, region from habse or container for ozone, did you get a chance to check recon ui ... View more

COuld you please confirm what is below in tmp dir looks like container to me, you can confirm the same form recon ui and find out the path it belongs to 405 GB /tmp/24c9e15e52afc47c225b757e7bee1f9d/ 134 GB /tmp/5af6b2617513b81608501adea4166625/ 21 GB /tmp/bc3dcd485adfa1c339eab38f1516c6c5/ ... View more

ozone admin namespace du ofs://<ozone nameservice>  please use this command ... View more

Hi @satvaddi  Thanks for connecting with cloudera, could you please let me know the current CDP version and whats the size of disk you provide for ozone, open your Recon webui and check if container has been created and it's the one storing the disk size i suspect this should be the case ... View more

HI Team, if you are storing the back in HDFS like above -rootPath file:/// [***DIRECTORY TO USE FOR BACKUP***]  then use the below command: hdfs dfs -du -s -h file:/// [***DIRECTORY TO USE FOR BACKUP***]  if its different storage like ozone(ofs/o3) then also hdfs command will work if its S3 then use the aws command ... View more

Hi Team, It does looks like too much data is writting to TS which causing it to reach 100%, did you check from TOP command how much kudu process is taking To fix it: 1. Please us the API in batch mode dont run all the jobs at one go as kudu works better in batch process 2. if possible reduce the load via increasing TS and data disk 3. Also check if any TP is running like antivirus which is not recommend and can cause a huge spike in CPU ... View more

1. Does it reduce the memory consumption once restart of this server 2. Leader master will have more consumption but in your case its look like a bug to me What is the CDH/CDP version you are using ... View more

Its Because of this Disk change where UUID of this TS was different but after change of WAL it created new one hence you seeing the wrong_server_UUID , simple restart of this TS will fix the issue in most of cases if not then please rebuild this TS from scratch while deleting the data and wal dir of this one it will solve the issue Note: Only proceed with rebuild if you have RF=3 in the cluster otherwise it will be a dataloss scenario ... View more

Hi Team, Leader master is the one who takes all front hit coming from client or connection so its obvious the consumption of Leader will be high ... View more