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

Add maxStalenessSeconds in readPreference between mongoS and config servers

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Catalog and Routing
    • 3

      I believe mongoS currently uses "nearest" without a maxStalenessSeconds option as the readPreference when communicating with the config server replica set. In the case where the "nearest" node is a lagged/stuck secondary, config reads (with afterCluserTime) may time out waiting for read concern. Adding a maxStalenessSeconds in the read preference mongoS uses seems to be an option. But I am wondering if mongoS already has other mechanism to retry such operations on a more up-to-date node.

            Assignee:
            Unassigned Unassigned
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: