Project

General

Profile

Actions
Copy link

Bug #46770

open

rgw incorrect http status on RADOS i/o error

Added by Or Friedmann almost 4 years ago. Updated over 3 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
Or Friedmann
Target version:
Ceph - v16.0.0
% Done:

0%

Source:
Development
Tags:
Backport:
nautilus octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
36428
Crash signature (v1):
Crash signature (v2):

Description

2020-07-30T11:20:29.492+0300 7fc47a684700 2 req 5 104.392984510s s3:get_obj op status=-110
2020-07-30T11:20:29.492+0300 7fc47a684700 2 req 5 104.392984510s s3:get_obj http status=200
2020-07-30T11:20:29.492+0300 7fc47a684700 1 ====== req done req=0x7fc6805e27a0 op status=-110 http_status=200 latency=104.392984510s ======

op status is -110 (timeout) and http status is 200, it looks like rgw is not sending any response in this situation (no packets on wireshark) although curl is still waiting for response

Related issues 1 (1 open — 0 closed)

Related to rgw - Bug #63206: beast: S3 download stalls without useful logs upon encountering an invalid RADOS objectNewShilpa MJ

Actions
Actions
Copy link

Also available in: Atom PDF