[
https://issues.apache.org/jira/browse/SAMZA-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570127#comment-14570127
]
Yan Fang commented on SAMZA-676:
--------------------------------
First attempt RB: https://reviews.apache.org/r/34974/
1. basically using the similar approach [~twbecker] mentioned: the same ssp is
assigned to multiple taskInstances. At the same time, modified the taskInstance
to allow it to skip already-processed-messages. This is useful because when
users relocate containers, difference taskInstances may have different offsets
for the broadcast stream. Using the oldest offset when the SSP has multiple
offsets.
2. also rewrite the Grouper classes with Java. added global streams when
grouping.
3. touched SAMZA-569 -- added a OffsetComparator for SystemAdmin
4. fixed SAMZA-699 -- changed to LinkedHashSet to preserve the order
5. modified the offsetManager to preserve the relation between
taskName-SSPs-offsets.
Looking for feedbacks! Thank you.
> 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,
> BroadcastStreamDesign_1.md, BroadcastStreamDesign_1.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)
