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

Check the possibility to remove read_preference/concern_unchanged tags from find_on_secondary.js

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2025-04-14, CAR Team 2025-04-28
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      The find_on_secondary.js is introduced in https://jira.mongodb.org/browse/SERVER-100833 to extend the test coverage for the project Terminate Secondary Reads on Range Deletion.

      The test find_on_secondary.js can't run on stepdown suites because it's tagged with `read_preference_unchanged` and `read_concern_unchanged`.

      The goal of this ticket is to investigate if it's feasible to remove these tags from the test.

      There are two proposals:

      • We can try to skip the override by using something similar to TestData.doNotOverrideReadPreference.
      • For the read concern, we can simply not use a read concern and expect to always get all the documents of the collection.

            Assignee:
            igor.praznik@mongodb.com Igor Praznik
            Reporter:
            igor.praznik@mongodb.com Igor Praznik
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: