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 2015/03/25 19:01:53 UTC

[jira] [Resolved] (SAMZA-335) Locality for Samza containers

     [ https://issues.apache.org/jira/browse/SAMZA-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Riccomini resolved SAMZA-335.
-----------------------------------
    Resolution: Duplicate

Resolving as dupe, since SAMZA-617 was opened.

> Locality for Samza containers
> -----------------------------
>
>                 Key: SAMZA-335
>                 URL: https://issues.apache.org/jira/browse/SAMZA-335
>             Project: Samza
>          Issue Type: Improvement
>          Components: container
>            Reporter: Chinmay Soman
>
> [Documenting my discussion with Jakob]
> There doesn't seem to be any 'data' locality for deploying containers. Today, this is done purely based on the free resources. It'll be nice to have some kind of locality with respect to the input streams. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)