[HADOOP-5881] Simplify configuration related to task-memory-monitoring and memory-based scheduling - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 0.20.1
Component/s: None
Labels:
None

Hadoop Flags:

Incompatible change, Reviewed

Description

The configuration we have now is pretty complicated. Besides everything else, the mechanism of not specifying parameters separately for maps and reduces leads to problems like HADOOP-5811. This JIRA should address simplifying things and at the same time solving these problems.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

HADOOP-5881-20090526-branch-20.1.txt
26/May/09 12:49
122 kB
Vinod Kumar Vavilapalli
HADOOP-5881-20090526.1.txt
26/May/09 10:16
123 kB
Vinod Kumar Vavilapalli

Issue Links

blocks

HADOOP-5883 TaskMemoryMonitorThread might shoot down tasks even if their processes momentarily exceed the requested memory

Resolved

incorporates

MAPREDUCE-140 TaskMemoryManager not enforcing memory limits in the presence of rogue tasks

Resolved

relates to

MAPREDUCE-1018 Document changes to the memory management and scheduling model

Closed

MAPREDUCE-516 Fix the 'cluster drain' problem in the Capacity Scheduler wrt High RAM Jobs

Closed

Activity

People

Assignee:: Vinod Kumar Vavilapalli

Reporter:: Vinod Kumar Vavilapalli

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 21/May/09 05:53

Updated:: 06/Apr/10 03:31

Resolved:: 27/May/09 06:04