You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/12/29 12:05:00 UTC

[jira] [Work logged] (BEAM-6329) State for portable timers can interfere with user state

     [ https://issues.apache.org/jira/browse/BEAM-6329?focusedWorklogId=179682&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-179682 ]

ASF GitHub Bot logged work on BEAM-6329:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Dec/18 12:04
            Start Date: 29/Dec/18 12:04
    Worklog Time Spent: 10m 
      Work Description: mxm commented on issue #7359: [BEAM-6329] Address synchronization issue for portable timers
URL: https://github.com/apache/beam/pull/7359#issuecomment-450488117
 
 
   Added the description to https://issues.apache.org/jira/browse/BEAM-6329
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 179682)
            Time Spent: 10m
    Remaining Estimate: 0h

> State for portable timers can interfere with user state
> -------------------------------------------------------
>
>                 Key: BEAM-6329
>                 URL: https://issues.apache.org/jira/browse/BEAM-6329
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>    Affects Versions: 2.9.0
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Critical
>              Labels: portability-flink
>             Fix For: 2.10.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The current active key needs to be set on Flink's state backend to support deleting pending timers on timer registration or firing. A keyed map for pending timers is necessary because Flink only allows deleting/resetting timers by their original time, not by their ids.
> Setting the current active key can interfere with accessing user-defined state, but can also interfere when a timer is set at the same time that a timer fires. In cases with a key initialized by the state requests, this would have caused pending timers to be associated with the wrong key which would have led to problems deleting / resetting them.
> Related to: BEAM-4681 BEAM-867



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)