You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Tao Feng (JIRA)" <ji...@apache.org> on 2016/04/15 05:58:25 UTC

[jira] [Updated] (SAMZA-833) ProcessJob mishandling containers

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

Tao Feng updated SAMZA-833:
---------------------------
    Attachment: SAMZA-833.4.patch

> ProcessJob mishandling containers
> ---------------------------------
>
>                 Key: SAMZA-833
>                 URL: https://issues.apache.org/jira/browse/SAMZA-833
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jake Maes
>            Assignee: Tao Feng
>         Attachments: SAMZA-833.1.patch, SAMZA-833.2.patch, SAMZA-833.3.patch, SAMZA-833.4.patch
>
>
> As a result of SAMZA-465 and SAMZA-805, ProcessJobFactory now passes the full config to the ProcessJob and no longer forces the container count to 1. This causes the ProcessJob to actually read the container count config and if it is not 1, it produces some unexpected behavior. 
> Specifically we've had reports of ProcessJobs dropping messages because the container count is > 1, so the grouper assigns partitions to more than 1 container, but only one container actually runs. 
> The goal of this ticket is to either force the container count to 1 for ProcessJob, or fix how multiple containers run with ProcessJob. But we should not allow the scenario where messages are dropped. 



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