Use non default 500 codes when storage node is time out #103

New Issue

Closed

opened 2023-05-02 14:38:51 +00:00 by alexvanin · 0 comments

alexvanin commented

2023-05-02 14:38:51 +00:00

Owner

S3 gateway sends requests to the storage node (object and tree services) and sometimes they fail with a timeout. We can use different HTTP code to notify client about that. This additional information allows better error handling mechanism on the client side. It might be useful for both load and functional tests.

S3 gateway sends requests to the storage node (object and tree services) and sometimes they fail with a timeout. We can use different HTTP code to notify client about that. This additional information allows better error handling mechanism on the client side. It might be useful for both load and functional tests.

alexvanin added this to the v0.28.0 milestone 2023-05-02 14:38:51 +00:00

alexvanin added the

good first issue

label 2023-05-02 14:38:51 +00:00

snegurochka added the

label 2023-05-03 17:15:01 +00:00

dkirillov self-assigned this 2023-06-13 14:16:50 +00:00

dkirillov referenced a pull request that will close this issue

2023-06-13 14:55:15 +00:00

[#103] Return 504 http code on timeout errors #138

alexvanin closed this issue

2023-06-14 15:46:31 +00:00

alexvanin referenced this issue from a commit

2023-06-14 15:46:31 +00:00

[#103] Return 504 http code on timeout errors

Sign in to join this conversation.

No Label

good first issue

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-s3-gw#103

There is no content yet.