Investigate capped collection tailing behavior on local collections

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Capped collections on the local database don't use so-called "metadata lock" that serializes write operations. This may be a problem for tailable cursors, which could skip over "holes". That is, the tailable cursors may skip over records that have not yet committed or are committed in a later snapshot.

      The oplog solves this problem by only showing records that are guaranteed to have no uncommitted writes before them.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: