[SAMZA-2304] Existing container locality mapping is incorrect when building job model

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0, 1.1, 1.2
• Fix Version/s: 1.3
• Assignee: Cameron Lee
• Reporter: Cameron Lee
• Created: 19/Aug/19 21:41
• Updated: 07/Nov/19 00:05
• Resolved: 30/Sep/19 16:59

Description

When building the job model, the existing container locality is read, so that the task to container grouping can be calculated. However, the existing container locality mapping is incorrect, in that it always has one extra container than the job container count. If a grouper (e.g. GroupByContainerIds) uses the mapping to figure out the container models, then it might return the incorrect number of containers for the job model.

Issue Links

• links to: GitHub Pull Request #1141