Bug #42634
closedrgw: expiration is triggered in advance because of an overflow problem
0%
Description
I set the lifecycle of a bucket to 30,000 days successfully, and then the expiration is triggered the next day. The objects in that bucket are deleted.
Because the lifecycle was successfully set to xattr, the problem may be in the process of determining whether the object has expired.
There is a variable named cmp in the function obj_has_expired which is used to determine if an object has expired.
cmp = days*24*60*60;
The data type of 'days' is int. When days == 30000, days*24*60*60 exceeds the range of data that int can represent.
In order to avoid this overflow problem caused by large 'days', the result on the right can be represented by a larger data type.
Updated by Casey Bodley over 4 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 31393
Updated by J. Eric Ivancich over 3 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to octopus,nautilus
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #48428: nautilus: rgw: expiration is triggered in advance because of an overflow problem added
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #48429: octopus: rgw: expiration is triggered in advance because of an overflow problem added
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".