Hello,
  The following is the scenario which caused this weird behavior. Is this
expected?

  - All maps tasks first completed successfully
  - Then all the reducers except 1 were completed.
  - While the last reduce task was running one of the tasktrackers died.
  - This made all the map tasks executed at that node to be moved to failed
  - The jobtracker re-assigned these map tasks to other nodes and the map
status is running.
  - The last reduce task finished execution, so I have reduce 100% but
maps running.

Is this correct to have maps running after reducers are completed?

- Prasad Pingali.
IIIT Hyderabad.


Reply via email to