| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
'simultaneous request bytes' limitations
configure s3 circuit breaker by 'command_s3_circuitbreaker.go':
usage eg:
# Configure the number of simultaneous global (current s3api node) requests
s3.circuit.breaker -global -type count -actions Write -values 1000 -apply
# Configure the number of simultaneous requests for bucket x read and write
s3.circuit.breaker -buckets -type count -actions Read,Write -values 1000 -apply
# Configure the total bytes of simultaneous requests for bucket write
s3.circuit.breaker -buckets -type bytes -actions Write -values 100MiB -apply
# Disable circuit breaker config of bucket 'x'
s3.circuit.breaker -buckets x -enable false -apply
# Delete circuit breaker config of bucket 'x'
s3.circuit.breaker -buckets x -delete -apply
|
|
ranged_request_invalid_range
ranged_request_empty_object
|
|
|
|
test_multi_objectv2_delete_key_limit
|
|
|
|
Protocol
Otherwise any requests to the underlying handlers results in calls to
ListObjects (v1) that may intensively load gateway and volume servers.
Added the following handlers with default responses:
- GetBucketLocation
- GetBucketRequestPayment
Added the following handlers with NotFound and NotImplemented responses:
- PutBucketAcl
- GetBucketPolicy
- PutBucketPolicy
- DeleteBucketPolicy
- GetBucketCors
- PutBucketCors
- DeleteBucketCors
|
|
|
|
|
|
fix https://github.com/chrislusf/seaweedfs/issues/2123
|
|
|
|
fix https://github.com/chrislusf/seaweedfs/issues/2075
|
|
fix https://github.com/chrislusf/seaweedfs/issues/2069
|
|
fix https://github.com/chrislusf/seaweedfs/issues/1545
|
|
* GetObjectTagging
* PutObjectTagging
* DeleteObjectTagging
|
|
fix https://github.com/chrislusf/seaweedfs/issues/1426
|
|
|