You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/07/15 23:29:04 UTC
[jira] [Commented] (SAMZA-336) Dynamic load balancing
[ https://issues.apache.org/jira/browse/SAMZA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062677#comment-14062677 ]
Chris Riccomini commented on SAMZA-336:
---------------------------------------
My current thoughts on this are documented here:
https://issues.apache.org/jira/browse/SAMZA-334?focusedCommentId=14062599&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14062599
> Dynamic load balancing
> ----------------------
>
> Key: SAMZA-336
> URL: https://issues.apache.org/jira/browse/SAMZA-336
> Project: Samza
> Issue Type: Improvement
> Components: container
> Affects Versions: 0.8.0
> Reporter: Chinmay Soman
>
> [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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)