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-9061) add entropy to s3 path for better scalability
Date Thu, 19 Jul 2018 00:52:00 GMT

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

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

Github user mdaxini commented on the issue:

    https://github.com/apache/flink/pull/6302
  
    @indrc 
    
    In addition to removing the additional dependency, I think there should be a test for
validating the randomness of the chose algorithm, and to make sure there are no conflicts.
For a Flink Job with large number of Task Managers and state in Terrabytes resulting in several
files, there could be a possibility of conflicts with the current random string generation
method. 
    
    fyi @StefanRRichter @StephanEwen 


> add entropy to s3 path for better scalability
> ---------------------------------------------
>
>                 Key: FLINK-9061
>                 URL: https://issues.apache.org/jira/browse/FLINK-9061
>             Project: Flink
>          Issue Type: Bug
>          Components: FileSystem, State Backends, Checkpointing
>    Affects Versions: 1.5.0, 1.4.2
>            Reporter: Jamie Grier
>            Assignee: Indrajit Roychoudhury
>            Priority: Critical
>              Labels: pull-request-available
>
> I think we need to modify the way we write checkpoints to S3 for high-scale jobs (those
with many total tasks).  The issue is that we are writing all the checkpoint data under a
common key prefix.  This is the worst case scenario for S3 performance since the key is used
as a partition key.
>  
> In the worst case checkpoints fail with a 500 status code coming back from S3 and an
internal error type of TooBusyException.
>  
> One possible solution would be to add a hook in the Flink filesystem code that allows
me to "rewrite" paths.  For example say I have the checkpoint directory set to:
>  
> s3://bucket/flink/checkpoints
>  
> I would hook that and rewrite that path to:
>  
> s3://bucket/[HASH]/flink/checkpoints, where HASH is the hash of the original path
>  
> This would distribute the checkpoint write load around the S3 cluster evenly.
>  
> For reference: https://aws.amazon.com/premiumsupport/knowledge-center/s3-bucket-performance-improve/
>  
> Any other people hit this issue?  Any other ideas for solutions?  This is a pretty
serious problem for people trying to checkpoint to S3.
>  
> -Jamie
>  



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

Mime
View raw message