[YARN-350] FSSchedulerNode is always instantiated with a 0 virtual core capacity

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.2-alpha
• Component/s: scheduler
• Assignee: Sandy Ryza
• Reporter: Sandy Ryza
• Created: 21/Jan/13 03:13
• Updated: 14/May/13 21:05
• Resolved: 14/May/13 21:05

Description

After YARN-2, FSSchedulerNode was not updated to initialize with the underlying RMNode's CPU capacity, and thus always has 0 virtual cores.

Issue Links

• duplicates: YARN-326 Add multi-resource scheduling to the fair scheduler