You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "David Anderson (Jira)" <ji...@apache.org> on 2022/06/17 13:09:00 UTC

[jira] [Updated] (FLINK-27910) FileSink not enforcing rolling policy if started from scratch

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

David Anderson updated FLINK-27910:
-----------------------------------
    Summary: FileSink not enforcing rolling policy if started from scratch  (was: FileSink not registered the timer to enforce rolling policy if started from scratch)

> FileSink not enforcing rolling policy if started from scratch
> -------------------------------------------------------------
>
>                 Key: FLINK-27910
>                 URL: https://issues.apache.org/jira/browse/FLINK-27910
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / FileSystem
>    Affects Versions: 1.15.0, 1.16.0
>            Reporter: Yun Gao
>            Assignee: Gen Luo
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.16.0, 1.15.1
>
>
> The current FileWriter only register the timer in initializeState, which is now only called on restoring. Thus if the job is started from scratch, the timer would fail to be registered and cause the rolling policy not work. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)