[
https://issues.apache.org/jira/browse/SAMZA-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544188#comment-14544188
]
Yan Fang commented on SAMZA-676:
--------------------------------
{quote}
When an envelope for an SSP comes in, it loops over all all tasks that SSP is
assigned to and passes the envelope to each of them.
{quote}
Aha, yeah, this is a good idea! It works under the assumption that, all the
tasks in the same container consume the broadcast stream at the same speed and
always read the same SSP messages. This assumption is not always true: If two
tasks run in different containers at the beginning and so have different
offsets for the broadcast stream (because, say, one container fails and then is
brought up), they are consuming the same stream in different speed. When they
are brought to one container, feeding them with the same messages seems not
ideal.
{quote}
Instead I simply made the RunLoop aware that a single SSP could map to
multiple task instances.
{quote}
curious how you let the RunLoop aware which SSP could map to multiple task
instances?
> Implement Broadcast Stream
> --------------------------
>
> Key: SAMZA-676
> URL: https://issues.apache.org/jira/browse/SAMZA-676
> Project: Samza
> Issue Type: Improvement
> Components: container
> Reporter: Yan Fang
> Assignee: Yan Fang
> Attachments: BroadcastStreamDesign.md, BroadcastStreamDesign.pdf
>
>
> There are a lot of discussion in SAMZA-353 about assigning the same SSP to
> multiple taskNames. This ticket is a subset of the discussion. Only focus on
> the broadcast stream implementation.
> The goal is to assign one SSP to all the taskNames.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
