Project

General

Profile

Actions

Bug #66438

closed

QuiesceDb: aggregate the TTL across members representing the same root as `max`

Added by Leonid Usov almost 2 years ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Backport:
squid
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
quiesce
Labels (FS):
Pull request ID:
Tags (freeform):
backport_processed
Fixed In:
v19.3.0-2867-gf7a3abb30f
Released In:
v20.2.0~2666
Upkeep Timestamp:
2025-11-01T01:36:05+00:00

Description

When the same root is included in multiple sets, the corresponding quiesce map should resolve the root TTL as a max between all values.

The rationale is that the TTL should be large enough to cover all aggregated states, as larger TTL values are harmless.

This defect is not a problem for the first release of the quiesce feature, as the TTL is not used in the current implementation.


Related issues 1 (0 open1 closed)

Copied to CephFS - Backport #66572: squid: QuiesceDb: aggregate the TTL across members representing the same root as `max`ResolvedPatrick DonnellyActions
Actions #1

Updated by Leonid Usov almost 2 years ago

  • Backport changed from sq to squid
Actions #2

Updated by Leonid Usov almost 2 years ago

  • Pull request ID set to 57980
Actions #3

Updated by Leonid Usov almost 2 years ago

  • Subject changed from QuiesceDb: aggregate the ttl across members as `max` to QuiesceDb: aggregate the TTL across members representing the same root as `max`
Actions #4

Updated by Leonid Usov almost 2 years ago

  • Status changed from New to Pending Backport
Actions #5

Updated by Upkeep Bot almost 2 years ago

  • Copied to Backport #66572: squid: QuiesceDb: aggregate the TTL across members representing the same root as `max` added
Actions #6

Updated by Upkeep Bot almost 2 years ago

  • Tags (freeform) set to backport_processed
Actions #7

Updated by Upkeep Bot 9 months ago

  • Status changed from Pending Backport to Resolved
  • Upkeep Timestamp set to 2025-07-08T18:35:44+00:00
Actions #8

Updated by Upkeep Bot 8 months ago

  • Merge Commit set to f7a3abb30fa4eb7fbfbe02a0acb00b42b837c96e
  • Fixed In set to v19.3.0-2867-gf7a3abb30f
  • Upkeep Timestamp changed from 2025-07-08T18:35:44+00:00 to 2025-08-02T04:50:53+00:00
Actions #9

Updated by Upkeep Bot 5 months ago

  • Released In set to v20.2.0~2666
  • Upkeep Timestamp changed from 2025-08-02T04:50:53+00:00 to 2025-11-01T01:36:05+00:00
Actions

Also available in: Atom PDF