Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3 read throughput slow down after hit prefix limit #1953

Open
shaowei-su opened this issue Mar 7, 2024 · 1 comment
Open

S3 read throughput slow down after hit prefix limit #1953

shaowei-su opened this issue Mar 7, 2024 · 1 comment

Comments

@shaowei-su
Copy link

shaowei-su commented Mar 7, 2024

Environment:

tensorflow==2.8.0
tensorflow-io==0.25.0

S3 loading client: tf.data.TFRecordDataset.

Issue

By default, S3 has limit on the number of GET/HEAD operation up to 5,500 per second per partitioned prefix, once this limit is reached than the read operation will throw 503 errors. What we noticed is that if the client starts seeing 503 error, the entire data loading speed will drop indefinitely until the end of the data loading process even if the 503 errors are recovered.

Question

Does the s3 client has retry logic in the case of 503 errors? if not, would failed S3 GET/HEAD request block the entire loading thread defined in num_parallel_reads field? Thanks

@cemlyn007
Copy link

Did you have any luck with this in the end? I also think I am experiencing this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants