[
https://issues.apache.org/jira/browse/SAMZA-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Chen updated SAMZA-1946:
--------------------------------
Summary: Problem with Race between TimerListener initialization and timers
fired from init() (was: Problem with Race between TimerListenener
initialization and timers fired from init())
> Problem with Race between TimerListener initialization and timers fired from
> init()
> -----------------------------------------------------------------------------------
>
> Key: SAMZA-1946
> URL: https://issues.apache.org/jira/browse/SAMZA-1946
> Project: Samza
> Issue Type: Bug
> Components: container
> Reporter: Rayman
> Assignee: Xinyu Liu
> Priority: Major
> Fix For: 1.1
>
>
> There are use cases where a Task reads from a rocksDB table in its init and
> sets timers.
> The problem is the TimerListener is initialized later in the
> task-initialization flow.
> This causes problems because invocations corresponding to timestamps in the
> past get ignored.
> One job is using this timer to issue re-transmissions to kafka (after reading
> the re-transmission list from rocksDB).
> So currently, on container-failoer, some of their retransmissions get ignored.
> Current hacky-fix is to add a 2-second offset to the timer-timestamps to try
> and ensure task-init and timerlistener completes before the timers-invocation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
