hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-17) Changing priority of a completed job causes problems in JobInProgressListeners
Date Sat, 31 Dec 2011 08:52:30 GMT

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

Harsh J resolved MAPREDUCE-17.
------------------------------

    Resolution: Not A Problem

This isn't an issue anymore. I've not noticed it with branch-1, nor is it an issue with MR2.
                
> Changing priority of a completed job causes problems in JobInProgressListeners
> ------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-17
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-17
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Hemanth Yamijala
>
> If the priority of a completed job is changed, a {{JobChangeEvent}} is raised and the
{{JobInProgressListeneners}}, like the capacity scheduler, are notified. Most implementations
handle the event by re-sorting their data structures, and thus could end up re-inserting the
completed job into their lists.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message