Skip to content

Commit c0d0b38

Browse files
Le0DeveloperOxyjun
andauthored
Update src/content/docs/r2/platform/troubleshooting.mdx
Co-authored-by: Jun Lee <[email protected]>
1 parent 5e1ccfb commit c0d0b38

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/docs/r2/platform/troubleshooting.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,6 @@ Track the number of concurrent requests to your bucket. If a client encounters a
5858

5959
If your users are directly uploading to the bucket (for example, using the S3 or Workers API), you may not be able to monitor or enforce a concurrency limit. In that case, we recommend bucket sharding.
6060

61-
### Bucket Sharding
61+
### Bucket sharding
6262

6363
For higher capacity at the cost of added complexity, consider bucket sharding. This approach distributes reads and writes across multiple buckets, reducing the load on any single bucket. While sharding cannot prevent a single hot object from exhausting capacity, it can mitigate the overall impact and improve system resilience.

0 commit comments

Comments
 (0)