flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aljoscha Krettek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7266) Don't attempt to delete parent directory on S3
Date Fri, 17 Nov 2017 12:41:00 GMT

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

Aljoscha Krettek commented on FLINK-7266:

We actually have to fix this for 1.4 because we regress from 1.3, otherwise. The operation
that deletes parent directories is too expensive and will basically DDOS s3, making Flink
unusable for bigger installations with s3.

> Don't attempt to delete parent directory on S3
> ----------------------------------------------
>                 Key: FLINK-7266
>                 URL: https://issues.apache.org/jira/browse/FLINK-7266
>             Project: Flink
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.3.1
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>            Priority: Blocker
>             Fix For: 1.4.0, 1.3.2, 1.5.0
> Currently, every attempted release of an S3 state object also checks if the "parent directory"
is empty and then tries to delete it.
> Not only is that unnecessary on S3, but it is prohibitively expensive and for example
causes S3 to throttle calls by the JobManager on checkpoint cleanup.
> The {{FileState}} must only attempt parent directory cleanup when operating against real
file systems, not when operating against object stores.

This message was sent by Atlassian JIRA

View raw message