[
https://issues.apache.org/jira/browse/MAPREDUCE-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karam Singh updated MAPREDUCE-1540:
-----------------------------------
Description:
Ran random writer, sort and sort validate job. Checked the jmap -histo:live and
verified that there is no reference of JobInProgress after Jobs are retired
Now submitter around 77 sleeps of around 10000 maps. then after 1 hr killed
all the job when jobs got retired. again checked jmap -histo:live for
JobInProgress for JT process found 2 references were there.
Found this while doing sanity testing of 1316
was:
Ran random writer, sort and sort validate job. Checked the jmap -histo:live and
verified that there is no reference of JobInProgress after Jobs are retired
Now submitter around 77 sleeps of around 10000 maps. then after 1 hr killed
all the job when jobs got retired. again checked jmap -histo:live for
JobInProgress for JT process found 2 references were there.
Found this while doing snaity testing of 1316
> Sometimes JobTracker holds stale refrence of JobInProgress even after Job
> gets retired
> --------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1540
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1540
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.20.2
> Reporter: Karam Singh
>
> Ran random writer, sort and sort validate job. Checked the jmap -histo:live
> and verified that there is no reference of JobInProgress after Jobs are
> retired
> Now submitter around 77 sleeps of around 10000 maps. then after 1 hr killed
> all the job when jobs got retired. again checked jmap -histo:live for
> JobInProgress for JT process found 2 references were there.
> Found this while doing sanity testing of 1316
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
