Investigate if a checkpoint cursor can be opened when a checkpoint is running

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Checkpoints, Cursors
    • None
    • Storage Engines, Storage Engines - Foundations
    • None
    • None

      From what I understand, a long-running checkpoint could block the creation of a checkpoint cursor. I believe it should open the last successful checkpoint but after looking at the code, it seems that it will return EBUSY if there is a checkpoint running and this EBUSY is handled and retried internally.

      See here and here where we set EBUSY and the internal loop here

      What needs to be done:

      • Create a test where we open a checkpoint cursor while a checkpoint is running
      • Add stats / logs when a checkpoint cursor cannot be opened

        1. test_checkpoint38.py
          3 kB
        2. ep_ftdc.png
          ep_ftdc.png
          139 kB

            Assignee:
            Unassigned
            Reporter:
            Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: