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

Remove sharding exceptions from invalidated_cursors FSM

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Query Execution
    • ALL
    • QE 2023-08-07, QE 2023-08-21, QE 2023-09-04, QE 2023-09-18, QE 2023-10-02, QE 2023-10-16, QE 2023-10-30, QE 2023-11-13, QE 2023-11-27, QE 2023-12-11, QE 2023-12-25, QE 2024-01-08

      In SERVER-33700 we decided to skip dropping database or dropping collection when the  invalidated_cursors.js FSM run on sharded clusters. The reason was that after doing those drops the test was failing to perform inserts with error "unable to target write op for collection ... caused by ... database not found".

      Originally we correlate this error to a bug affecting dropping collections/databases on sharded cluster SERVER-17397. Considering that this bug have been fixed in 5.0 we should now remove these exceptions in the test.

            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            tommaso.tocci@mongodb.com Tommaso Tocci
            0 Vote for this issue
            6 Start watching this issue