[ https://issues.apache.org/jira/browse/YARN-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhihai xu updated YARN-2376: ---------------------------- Attachment: YARN-2376.000.patch > Too many threads blocking on the global JobTracker lock from getJobCounters, > optimize getJobCounters to release global JobTracker lock before access the > per job counter in JobInProgress > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: YARN-2376 > URL: https://issues.apache.org/jira/browse/YARN-2376 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: zhihai xu > Assignee: zhihai xu > Attachments: YARN-2376.000.patch > > > Too many threads blocking on the global JobTracker lock from getJobCounters, > optimize getJobCounters to release global JobTracker lock before access the > per job counter in JobInProgress. It may be a lot of JobClients to call > getJobCounters in JobTracker at the same time, Current code will lock the > JobTracker to block all the threads to get counter from JobInProgress. It is > better to unlock the JobTracker when get counter from > JobInProgress(job.getCounters(counters)). So all the theads can run parallel > when access its own job counter. -- This message was sent by Atlassian JIRA (v6.2#6252)