English description of why critical section is a transaction by design

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2025-03-31, CAR Team 2025-04-14, CAR Team 2025-04-28, CAR Team 2025-05-12, CAR Team 2025-05-26, CAR Team 2025-06-09, CAR Team 2025-06-23, CAR Team 2025-07-07, CAR Team 2025-07-21, CAR Team 2025-08-04, CAR Team 2025-08-18, CAR Team 2025-09-01, CAR Team 2025-09-15, CAR Team 2025-09-29
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The protocols that modify the catalog information often do so under a critical section (CS). The system's design treats the CS as a transaction. Yet, the CS is composed of several sub-parts with individually noticeable effects. We need a clear description of why the critical section transposes into a transaction as per its implementation and how doing so keeps our protocols correct.

            Assignee:
            Sergi Mateo Bellido
            Reporter:
            Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: