You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Vinod K V (JIRA)" <ji...@apache.org> on 2008/10/08 15:20:44 UTC

[jira] Created: (HADOOP-4375) Accesses to CompletedJobStore should not lock the JobTracker.

Accesses to CompletedJobStore should not lock the JobTracker.
-------------------------------------------------------------

                 Key: HADOOP-4375
                 URL: https://issues.apache.org/jira/browse/HADOOP-4375
             Project: Hadoop Core
          Issue Type: Bug
            Reporter: Vinod K V



When CompletedJobStatusStore is configured to use dfs, it can cause lockup of JT due to inline dfs access.
For e.g.
{code}
  public synchronized JobStatus getJobStatus(JobID jobid) {
    JobInProgress job = jobs.get(jobid);
    if (job != null) {
      return job.getStatus();
    } else {
      return completedJobStatusStore.readJobStatus(jobid);
    }
  }
{code}

Instead, JT should be locked only when accessing its internal memory structures. The other such methods are JobTracker.getJobCounters, JobTracker.getJobProfile and JobTracker.finalizeJob.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (HADOOP-4375) Accesses to CompletedJobStore should not lock the JobTracker.

Posted by "Vinod K V (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod K V resolved HADOOP-4375.
-------------------------------

    Resolution: Duplicate

HADOOP-5285 fixed this.

> Accesses to CompletedJobStore should not lock the JobTracker.
> -------------------------------------------------------------
>
>                 Key: HADOOP-4375
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4375
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Vinod K V
>
> When CompletedJobStatusStore is configured to use dfs, it can cause lockup of JT due to inline dfs access.
> For e.g.
> {code}
>   public synchronized JobStatus getJobStatus(JobID jobid) {
>     JobInProgress job = jobs.get(jobid);
>     if (job != null) {
>       return job.getStatus();
>     } else {
>       return completedJobStatusStore.readJobStatus(jobid);
>     }
>   }
> {code}
> Instead, JT should be locked only when accessing its internal memory structures. The other such methods are JobTracker.getJobCounters, JobTracker.getJobProfile and JobTracker.finalizeJob.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.