[jira] [Updated] (SAMZA-1946) Problem with Race between TimerListenener initialization and timers fired from init()

["Jake Maes (JIRA)" <ji...@apache.org>]

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

Jake Maes updated SAMZA-1946:
-----------------------------
    Fix Version/s: 1.0.1
                   1.0.1

> Problem with Race between TimerListenener 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.0.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)