[ 
https://issues.apache.org/jira/browse/HADOOP-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amareshwari Sriramadasu updated HADOOP-5486:
--------------------------------------------

        Fix Version/s:     (was: 0.21.0)
                       0.20.0
    Affects Version/s: 0.20.0
         Hadoop Flags: [Incompatible change]
               Status: Patch Available  (was: Open)

test-patch result :
{noformat}
     [exec]
     [exec] -1 overall.
     [exec]
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]
     [exec]     -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
     [exec]                         Please justify why no tests are needed for 
this patch.
     [exec]
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec]
     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
     [exec]
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
     [exec]
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath 
integrity.
     [exec]
     [exec]     +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
     [exec]
     [exec]
{noformat}

Ran MRReliabilityTest and verified it tests lostTrackers

> ReliabilityTest does not test lostTrackers, some times.
> -------------------------------------------------------
>
>                 Key: HADOOP-5486
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5486
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred, test
>    Affects Versions: 0.20.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.20.0
>
>         Attachments: patch-5486.txt
>
>
> ReliabilityTest does not lose trackers, if tasktracker pid could not be 
> obtained.  If command for the TaskTracker process is large, doing 'ps' and 
> 'grep' does not return the pid of the process, thus it could not be suspended.

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

Reply via email to