Member since
03-07-2016
55
Posts
3
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
8366 | 07-27-2016 09:44 AM | |
12188 | 05-02-2016 05:24 PM |
07-27-2016
09:44 AM
If you are referring to MapReduce Job History Server by JH, JHS has its own job ACL control. If a MR job is configured with mapreduce.job.acl-view-job = {users you want to allow to view the job, see mapred-default.xml for details on format} Then JHS will allow the specified user to view the job.
... View more
05-19-2016
10:13 AM
Sorry, missed the point that the issue can be reproduced 100%. In CDH5.4, both YARN and MR have some bugs that together in some cases, can cause deadlock or jobs to slow down dramatically. In your case, it is more likely the latter. Keep us posted on how CDH5.7 behaves.
... View more
05-18-2016
06:57 PM
Sounds a lot like a deadlock problem in MapReduce. The only solution I can think of is to kill the job and start over. Because the chances of getting into a deadlock are very rare, the job should be able to progress at the second run. The deadlock problem has been seen in 5.7 as well. Until it is completely solved in apache hadoop, it will stay for a while.
... View more
05-04-2016
07:23 PM
Is it possible for you to try the same settings in your production cluster? If your dev cluster is very close to production server in terms of workload, then I'd guess this will alleviate gc pause in your production cluster as well.
... View more
05-02-2016
06:04 PM
http://stackoverflow.com/questions/9257361/how-to-check-heap-size-allocated-for-jvm-by-linux
... View more
05-02-2016
05:24 PM
you will need to append " -Xms512m -Xmx1024m -XX:PermSize=216m -XX:MaxPermSize=512m " to the property Java Configuration Options for Node Manager, and then restart Node Managers. You'll want to change the numbers for -Xmx and -XX:MaxPermSize to values bigger than what you currently have for Node Manager. Please try to do this in a test enviroment first as this may impact on your production cluster.
... View more
05-02-2016
04:19 PM
Which version of java are you using? I do not know much about GC tuning, but heap size can lead to GC pause sometimes, you can try to increaes the heap size of Node Manager if that is possible. You can also try to collect gc logs by adding java options temporarily "-XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -XX:+PrintGCApplicationStoppedTime -XX:PrintFLSStatistics=2"
... View more
05-02-2016
03:12 PM
Jais, for some reason, the configuration is not visiable to me. Can you copy and paste it here as text?
... View more
05-02-2016
02:16 PM
What is exactly the role that had this warning message?
... View more