have seen the execution summary ,its taking 15 mins and after that query is getting cancelled.have already done compute stats for involved tables. there is no memory problem as it shows consumption 340 MB out of 35 GB of memory. ... View more

I notice that yarn.resourcemanager.max-completed-applications is set to 10,000 which almost the running application for 2-3 days.   I want to increase the number to 40,000 to cover the retention of 7 days, what other changes i should take inot consideration? should i increase the jaba heap size for the resources manager? should i change any other configuration at the level od node manager? what i should monitor after increasing max completed applications to 40,000? how this make impact the resource manager recovery performance?   Thanks in advance. ... View more

@Telematics,     In Cloudera Manager, edit Proxy User Configuration  What did you enter in the field? It should look like this, for example: joe=alice,bob;hue=*;admin=*   See the Description of Proxy User Configuration in Cloudera Manager (click the question mark next to the property)   -Ben ... View more

I figured out the issue.   The diffetence comes from /tmp/logs.   Weird why hdfs dfs -du -h -s / is not considering /tmp/logs. ... View more

Don't know the exact cause that it was not working even i restarted the Yarn, when i had another chance to restart the Yarn, the issue was resolved. ... View more

@Harsh J For my special case where the hadoop nodes uptime was 1200 days and the servers with old centos versions, restarted the servers took the inodes down from 88% to 10%. ... View more

You could use 'tinker step 500' and have the effect that stepping would only be enabled for time differences more than 500ms. I wouldn't consider this breaking your production environment, but I guess you may have some reason that '-x' is important to you. We'll work on addressing this in a future release so that no system-wide changes are necessary. -Todd ... View more

@mbigelow thats wright! the app used an older API from MRv1. The app uses almost the same amount of data each day plus aprox 30GB so the expected time could be a little bit more each day, as the app runs daily, but in the last days past from 9 hours to more than a day to finish. The solution I've founded was to decrease the amount of memory instead of increase it. Now the app can allocate more containers so the app is runing pretty fast. Thanks for your help, just in case I'll let you know. Guido.   ... View more