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

mongos must fassert when presented with IncompatibleWithUpgradedServer

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: In Progress
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.3 Required
    • Component/s: Networking, Sharding
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Service Arch 2019-09-09, Service Arch 2019-09-23, Service Arch 2019-10-07, Service Arch 2019-10-21

      Description

      Before SERVER-35688, the ShardingTaskExecutor was able to observe IncompatibleWithUpgradedServer, thus preventing indefinite waits when a mongos connected to a newer mongod with a higher fcv. That ticket changed the RSM so that rather than using dbclient to do scans, we instead used a task executor, which in turn changed things so that rather than failing, we repeatedly retry the connect.

      We should probably do one of:

      • move the check that's currently in the ShardingTaskExecutor into some other lib that we can link into the regular task executor, so that all task executors in sharding exhibit the correct behavior
      • change the RSM to have a network connect hook which crashes on that status (in sharding)

      I'm on the fence which is less invasive

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: