Hi @lysConsulting The No route to host indicates that there is a network issue between this client and the HDFS cluster. I would suggest to check if the basic networking is working fine between these hosts.  ... View more

HI @Felix-Han Based on the Error, it seems there are too many request coming to that specific Region server thereby consuming the handlers it has.   So may want to check if multiple clients are hitting the same Region server ( hotspot) or try to raise the handler count.   https://my.cloudera.com/knowledge/CallQueueTooBigException--Call-queue-is-full-on-000060020-too?id=73901 ... View more

Hi @mazz , Check if the below article helps you in achieving this. You will need to modify the duration.   https://community.cloudera.com/t5/Support-Questions/How-to-do-a-cleanup-of-hdfs-files-older-than-a-certain-date/m-p/182146 ... View more

Hi @mike_bronson7 , The thumb rule is to have 1 Gb of heap allocated to 1 Million block. Now, as you have already doubled the heap, I think you can check on improving the garbage collector tunings.   https://community.cloudera.com/t5/Community-Articles/NameNode-Garbage-Collection-Configuration-Best-Practices-and/ta-p/245276   You can try tunings the GC threads to see if that helps. Been said that, these pauses are not very huge to cause any real trouble and we don't see it repeating very frequently ( within mins) and can be expected on a busy Cluster.   You can also check if the threshold to report a JVM pause alert can be adjusted to say 5-10 secs which needs some intervention. ... View more

Hi @hanumanth , The network bandwidth needs to be limited at the OS side using the tools such as traffic control (tc) which can be set on the NIC which carries the ip address for the CDH roles.   For info on this can be found in the Red Hat docs : https://access.redhat.com/solutions/69133 https://access.redhat.com/solutions/1324033     ... View more

Hi @fengsh Yes, The remove script indeed has few bugs using curl which was picked up from AMBARI-18435 but this curl call is not officially supported and as such we don't have an official doc on this.   The other option to remove the older stack with "yum remove <version>" command, specifying the exact version you want to remove should get the job done.   You can also verify the list of packages to be removed using (please be thorough!): # yum list installed | grep -P 'version'   Additionally, please verify the symlinks in the "/usr/hdp/current/" folder are pointing to the correct location.   -- Was your question answered? Please take some time to click on “Accept as Solution” below this post. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more