Bug #61817: Ceph swift error: create container return 404; - rgw - Ceph

Actions

Copy link

Bug #61817

closed

Ceph swift error: create container return 404;

Added by Charlie Ouyang 10 months ago. Updated 4 months ago.

Status:

Can't reproduce

Priority:

Normal

Assignee:

Target version:

Ceph - v14.2.23

% Done:

Source:

Community (user)

Tags:

Backport:

Regression:

Severity:

2 - major

Reviewed:

Affected Versions:

Ceph - v10.2.9

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

Hi, team;

I'm using javaswift to access ceph-swift, but got an unexpected error, here are the client logs:

Caused by: org.javaswift.joss.exception.CommandException: null
at org.javaswift.joss.command.impl.core.httpstatus.HttpStatusChecker.verifyCode(HttpStatusChecker.java:45)
at org.javaswift.joss.command.impl.core.AbstractCommand.call(AbstractCommand.java:50)
at org.javaswift.joss.command.impl.core.AbstractSecureCommand.call(AbstractSecureCommand.java:31)
at org.javaswift.joss.client.core.AbstractContainer.create(AbstractContainer.java:221)
at com.sequoiacm.cephswift.dataservice.CephSwiftDataService.createContainer(CephSwiftDataService.java:132)
... 117 common frames omitted

Then I check ceph.rgw logs, it shows:

2023-03-16 10:34:11.822 7f8bdc27e700 1 beast: 0x7f8b914cf6c0: 192.168.28.137 - - [2023-03-16 10:34:11.0.822342s] "PUT /swift/v1/ws_pool_new_2_scmfile_202303 HTTP/1.1" 202 0 - "Apache-HttpClient/4.5.5 (Java/1.8.0_152)" -
2023-03-16 10:34:11.824 7f8c3fb45700 1 beast: 0x7f8b9134c6c0: 192.168.28.137 - - [2023-03-16 10:34:11.0.824342s] "PUT /swift/v1/ws_pool_new_2_scmfile_202303 HTTP/1.1" 404 9 - "Apache-HttpClient/4.5.5 (Java/1.8.0_152)" -
2023-03-16 10:34:11.824 7f8bf3aad700 1 ====== starting new request req=0x7f8b914cf6c0 =====
2023-03-16 10:34:11.824 7f8c2fb25700 1 ====== req done req=0x7f8b910466c0 op status=-2 http_status=404 latency=0.469999s

It seems that when I try to create container then got a 404.
No information can be analyzed from the log, so I am wondering what caused the 404, and whether there is a way to avoid it.

Reproduce: create more enough threads to create a same container.