Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-92239

change streams don't survive stepdowns when a rollback also occurs.

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • ALL
    • v8.0, v7.0, v6.0, v5.0
    • QE 2024-07-22, QE 2024-08-05, QE 2024-08-19, QE 2024-09-02, QE 2024-09-16, QE 2024-09-30, QE 2024-10-14, QE 2024-10-28, QE 2024-11-11
    • 30

      when a rollback occurs the catalog is reopened and all queries are "killed" during restore state. example: https://github.com/mongodb/mongo/blame/0f03a87838e10c3add85d11298cd289069c3c4ce/src/mongo/db/exec/requires_collection_stage.cpp#L90 we know change streams are safe to continue since they only return majority reads so they could continue, but a simpler option might be to just make this error resumable so that the client automatically retries the change streams

            Assignee:
            mindaugas.malinauskas@mongodb.com Mindaugas Malinauskas
            Reporter:
            mickey.winters@mongodb.com Mickey Winters
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: