Bug #46770
openrgw incorrect http status on RADOS i/o error
0%
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
Updated by Or Friedmann over 3 years ago
It happens after implementing objecter timeout, but it will probably occur on any error come from RADOS in iterate_obj
Updated by Or Friedmann over 3 years ago
As the status code sent before sending the body it is not possible to change the http_status.
It looks like Civetweb closes the response as it should and Beast doesn't
Updated by Matt Benjamin over 3 years ago
Thanks, I wonder if Marcus ran into this.
Matt
Updated by Casey Bodley over 3 years ago
It looks like Marcus did address this on the read side in https://github.com/ceph/ceph/pull/35350.
Updated by Casey Bodley 4 months ago
- Related to Bug #63206: beast: S3 download stalls without useful logs upon encountering an invalid RADOS object added