Decouple Ticket class from AdmissionContext to enforce use of snapshotted priority

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2025-10-13, CAR Team 2025-11-10
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      A Ticket object snapshots an operation's priority upon entering the storage engine, and this snapshot is correctly used for metrics when the ticket is released.

      However, the Ticket class currently holds a reference to the entire AdmissionContext, creating a risk that future code changes might incorrectly use the live priority from the context instead of the snapshotted value, leading to inaccurate metrics.

      To harden the code and prevent any potential bug, the pointer to AdmissionContext should be removed from the Ticket class, ensuring it only stores the specific values it needs directly.

            Assignee:
            Pol Pinol
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: