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

Check the possibility to bypass the prohibition of using getMore in long_secondary_reads.js

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2025-04-14
    • 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 and to test how a long-running queries behave when there are chunk migrations in the background.

      However, an error is thrown whenever a test tries to call the getMore command because there is no mechanism yet to handle retries due to chunk migrations. Therefore, we had to exclude the test from balancer suites using the requires_getmore tag.

      The plan is to skip the retry logic on network error using the withSkipRetryOnNetworkError() handler, similar to what this test does, and handle the retry logic on the test itself.

            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:
              Resolved: