From 92e9f6564e8de63e2052ea5dc5ea8d23c1be260e Mon Sep 17 00:00:00 2001 From: Justin James Date: Wed, 25 Sep 2024 12:45:10 -0400 Subject: [PATCH] code review changes --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9b49485..684712b 100644 --- a/README.md +++ b/README.md @@ -233,9 +233,9 @@ To increase or decrease the logging level for the S3 plugin, add an `s3_resource ### Handling Reduce Your Request Rate Errors -On operations that require a checksum calculation to an S3 object at rest, iRODS must read the object's data to calculate the checksum. The default buffer size for these reads is 1 MiB. Each of these read requests map to a separate GetObject request to S3 with a range of bytes. This can exceed the request rate that the S3 provider allows. +On operations that require calculating a checksum for an S3 object at rest, iRODS must read the object's data to calculate the checksum. The default buffer size for these reads is 1 MiB. Each of these read requests map to a separate GetObject request to S3 with a range of bytes. This can exceed the request rate that the S3 provider allows. -To resolve this problem, the read buffer size can be increased by updating the `checksum_read_buffer_size_in_bytes` value in the `advanced_settings` stanza of server_config.json. +To resolve this problem, the read buffer size can be increased by updating the `checksum_read_buffer_size_in_bytes` value in the `advanced_settings` stanza of server_config.json. This change should be made for all servers that can serve requests to that S3 resource. The following is an example of increasing this buffer size to 10 MiB: