Project

General

Profile

Actions

Feature #64083

open

Response code from rgw rate-limit should be 429 not 503 , best is configurable

Added by hoan nv 4 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

My cluster in 17.2.6 version.

I use rate-limit features https://docs.ceph.com/en/quincy/radosgw/admin/#rate-limit-management

After set rate limit for some user.

I see haproxy logs will see logs 503 status and rgw logs sometime like that

{"bucket":"veeam-test","time":"2024-01-15T22:23:35.975848Z","time_local":"2024-01-15T22:23:35.975848+0000","remote_addr":"171.244.32.2","user":"test","operation":"put_obj","uri":"PUT /veeam-test/Veeam/Archive/veeam-116/ae1cb961-764c-46ae-aef3-ba0668dfa008/a79fe84c-1cd3-44a2-a8b2-125e73026d0b/blocks/4113564ad3ca58f60d64e45d7c1f51ac/154616.6a4eb5930f72b2e1a75d43a34cca03f7.00000000000000000000000000000000.blk HTTP/1.1","http_status":"503","error_code":"SlowDown","bytes_sent":231,"bytes_received":0,"object_size":0,"total_time":1,"user_agent":"APN/1.0 Veeam/1.0 Backup/11.0","referrer":"","http_x_headers":[{"HTTP_CONTENT_MD5":"IK/uASkXx8yIDwmQtl0ZcQ=="},{"HTTP_X_FORWARDED_FOR":"171.244.32.2"}],"trans_id":"tx000008b76ec0eab2e0249-0065a5b067-1c21258-sgn10-1","authentication_type":"Local","access_key_id":"xxxxx","temp_url":false}

Status 429 will be match response code from rate-limit :

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429

I think this config should be configurable like :

rgw_rate_limit_response_status = 429

Thanks.

Actions #1

Updated by Wes Dillingham about 2 months ago

+1 on this request

Actions

Also available in: Atom PDF