Bug #62808
closedBuckets mtime equal to creation time
0%
Description
All nodes running ceph version 18.2.0 (5dd24139a1eada541a3bc16b6941c5dde975e26d) reef (stable)
On my last 17.2.6 setup, all mtimes were showing Dec 31 1969. On reef, the mtime is returned as the bucket creation time, which is also incorrect. This is in the RGW dashboard as well as radosgw-admin bucket stats.
{
"bucket": "1631126535376.syfdcajseixi4bzko-1663261319561.cv3irh0ek4i3v3eiu",
"num_shards": 11,
"tenant": "",
"zonegroup": "5a135b22-dd05-40cb-bc15-1794cf992a48",
"placement_rule": "NBDFS.C3-EC",
"explicit_placement": {
"data_pool": "",
"data_extra_pool": "",
"index_pool": ""
},
"id": "68f0a0f3-588c-43d3-9c6d-6f3da43f02ab.5267618.2",
"marker": "68f0a0f3-588c-43d3-9c6d-6f3da43f02ab.5267618.2",
"index_type": "Normal",
"owner": "1631126535376.syfdcajseixi4bzko",
"ver": "0#3942,1#3565,2#3811,3#3478,4#3508,5#3750,6#3578,7#3644,8#3970,9#3805,10#3496",
"master_ver": "0#0,1#0,2#0,3#0,4#0,5#0,6#0,7#0,8#0,9#0,10#0",
"mtime": "2023-05-19T00:32:00.588250Z",
"creation_time": "2023-05-19T00:31:58.210866Z",
"max_marker": "0#,1#,2#,3#,4#,5#,6#,7#,8#,9#,10#",
"usage": {
"rgw.main": {
"size": 73790430311,
"size_actual": 73799258112,
"size_utilized": 7379043 0311,
"size_kb": 72060968,
"size_kb_actual": 72069588,
"size_kb_utilized": 72060968,
"num_objects": 5671
},
"rgw.multimeta": {
"size": 0,
"size_actual": 0,
"size_utilized": 0,
"size_kb": 0,
"size_kb_actual": 0,
"size_kb_utilized": 0,
"num_objects": 0
}
},
"bucket_quota": {
"enabled": false,
"check_on_raw": false,
"max_size": -1,
"max_size_kb": 0,
"max_objects": -1
}
}
How can we get back to the behavior we had on Pacific and prior with correct bucket mtimes?
Updated by Alex Yarbrough 8 months ago
Actually even on 17.2.5 the mtime was correct.
Updated by Daniel Gryniewicz 8 months ago
Looking at the code, it looks like pacific was working, 17.2.5 was broken, and 17.2.6 (and reef) are working correctly. In the output you gave, the mtime and creation time are different. Can you clarify?
Updated by Alex Yarbrough 8 months ago
My mistake. In the listed output, the mtime and creation_time are off slightly by <2 seconds, but the date is May 19, 2023.
Data is being placed in this bucket every day. I would expect the date portion of mtime to be September 14, 2023.
Updated by Casey Bodley 7 months ago
- Status changed from New to Need More Info
Alex Yarbrough wrote:
Data is being placed in this bucket every day. I would expect the date portion of mtime to be September 14, 2023.
the bucket's mtime would not be updated every time you upload an object. some bucket operations like PutBucketAcl may be expected to update the mtime, but it's not exactly clear which ops expect that
Updated by Casey Bodley about 2 months ago
- Status changed from Need More Info to Can't reproduce