[SAMZA-336] Dynamic load balancing

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.8.0
• Component/s: container
• Assignee: Unassigned
• Reporter: Chinmay Soman
• Created: 15/Jul/14 17:31
• Updated: 15/Jul/14 21:28

Description

[Documenting my discussion with Jacob]

Lack of resources (eg: memory) might lead to a particular container lagging behind. In the current implementation, this leads to the container dying and restarting with the same config.

A better strategy would be to split the work into additional containers (maybe) and then partition the job further. This is definitely possible for stateless jobs. However, whether the same can be accomplished for stateful jobs - needs to be investigated.

Issue Links

• relates to: SAMZA-334 Need for asymmetric container config