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, 23 Aug 2018 16:16:00 GMT

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

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

StefanRRichter commented on issue #6604: [FLINK-9061] Optionally add entropy to checkpoint
paths better S3 scalability
URL: https://github.com/apache/flink/pull/6604#issuecomment-415476287
 
 
   Modulo some test failures from NPEs.

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


> 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