Commit e2b43be
committed
rgw/lc: enforce consistent rgw_lc_debug_interval start times
when configured, rgw_lc_debug_interval causes lifecycle processing to
run every interval. but different workers/radosgws could start these
intervals at different times, making it difficult for already_run_today()
to determine which buckets should be skipped in the current interval
schedule_next_start_time() now chooses start times (in seconds since
epoch) that are divisible by the rgw_lc_debug_interval to ensure that
all workers use the same intervals
already_run_today() uses this same logic to calculate the beginning of
its current interval for comparison with the last time the bucket's
processing started
Fixes: https://tracker.ceph.com/issues/72943
Signed-off-by: Casey Bodley <[email protected]>1 parent 25577cd commit e2b43be
1 file changed
+9
-7
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2250 | 2250 | | |
2251 | 2251 | | |
2252 | 2252 | | |
2253 | | - | |
2254 | | - | |
2255 | | - | |
2256 | | - | |
2257 | | - | |
| 2253 | + | |
| 2254 | + | |
| 2255 | + | |
| 2256 | + | |
| 2257 | + | |
2258 | 2258 | | |
2259 | 2259 | | |
2260 | 2260 | | |
| |||
2642 | 2642 | | |
2643 | 2643 | | |
2644 | 2644 | | |
2645 | | - | |
2646 | | - | |
| 2645 | + | |
| 2646 | + | |
| 2647 | + | |
| 2648 | + | |
2647 | 2649 | | |
2648 | 2650 | | |
2649 | 2651 | | |
| |||
0 commit comments