flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-9325) generate the _meta file for checkpoint only when the writing is truly successful
Date Mon, 20 Aug 2018 17:05:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-9325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586228#comment-16586228
] 

ASF GitHub Bot commented on FLINK-9325:
---------------------------------------

sihuazhou commented on issue #5982: [FLINK-9325][checkpoint]generate the meta file for checkpoint
only when the writing is truly successful
URL: https://github.com/apache/flink/pull/5982#issuecomment-414390311
 
 
   Hi @StephanEwen thanks for your comments! I was caught up by some terrible work recently,
will have look at the `RecoverableFsDataOutputStream` and get back here probably this weekend.
;)

----------------------------------------------------------------
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


> generate the _meta file for checkpoint only when the writing is truly successful
> --------------------------------------------------------------------------------
>
>                 Key: FLINK-9325
>                 URL: https://issues.apache.org/jira/browse/FLINK-9325
>             Project: Flink
>          Issue Type: Improvement
>          Components: State Backends, Checkpointing
>    Affects Versions: 1.5.0
>            Reporter: Sihua Zhou
>            Assignee: Sihua Zhou
>            Priority: Major
>              Labels: pull-request-available
>
> We should generate the _meta file for checkpoint only when the writing is totally successful.
We should write the metadata file first to a temp file and then atomically rename it (with
an equivalent workaround for S3). 



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

Mime
View raw message