Hi @snm1523 , correct you have to manually delete those files in HDFS, we are aware of it and currently we are working on that issue. ... View more

Hi @snm1523 those configs are for spool directories, these configs won't help you. The audit logs are stored in HDFS, It's Solr collections that will store them in HDFS, if your solr is configured to store them in HDFS then by default all the auditing will happen in HDFS. You can refer to the below doc to check where and how solr collections are stored.   https://docs.cloudera.com/cdp-private-cloud-base/7.1.8/security-ranger-auditing/topics/security-ranger-audit-migrating-storage-data-location.html     ... View more

Hi @soumM can you please check if both the cluster nodes are in /etc/hosts file on each node.   We need a full error stack to debug this. ... View more

Hi @josr89 you need to look at name node logs for the ranger plugin sync up, basically every service runs a ranger policy refresher which will sync the policies from the ranger, it's kind of a pull architecture, services will pull policies from ranger and store them in its cache. So try looking at Name node logs and search for ranger refresher logs that should give you some idea. ... View more

Hi, @Juanes this might also be coming from the DNS side, check the agent logs for any DNS test failures and try to do nslookup from another node to this node IP address and then HQDN and check whether the DNS server is resolving the hostname and IP address correctly or not. as @upadhyayk04 suggested try the #hostname -f or #hostnamectl commands to get the correct FQDN. # nslookup <IP-address>/FQDN - if this is not resolving correctly then you may need to check the DNS server whats happening. ... View more

Hi @yagoaparecidoti please try the below API call with a view as FULL_WITH_HEALTH_CHECK_EXPLANATION parameter, please change the cluster name, host IP, API version etc, this should show all the kinds of health test running on the cluster. curl -X GET "http://10.129.116.234:7180/api/v54/clusters/xsczx/services?view=FULL_WITH_HEALTH_CHECK_EXPLANATION" -H "accept: application/json" ... View more

Hi @datafiber it seems like your Namenode is in Safe mode, not sure why it went into safe mode, but you can try taking it out manually and then retry the operation and monitor the logs.   run the below commands from NN. # hdfs dfsadmin -safemode leave # hdfs dfsadmin -safemode status   ... View more

Hi, @user2024 I don't the canary file is gonna cause this issue, the blocks that are corrupt/missing are now lost and cannot be recovered, you can manually delete those blocks by identifying them using the below command and run the hdfs balancer on HDFS so that NN will balance the new blocks across the cluster. # hdfs fsck -list-corruptfileblocks You can also refer to the below article. https://stackoverflow.com/questions/19205057/how-to-fix-corrupt-hdfs-files ... View more