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

Prevent config.system.sessions from being sharded with incorrect options

XMLWordPrintableJSON

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

      Although we generally expect the sessions collection to be created internally by the logical sessions cache refresher, the user does have the option to create it manually if it does not exist (TSEs sometimes do this if there are problems with the sessions collection if thy drop it).

      We do not enforce that it must be created with the expected shard key (_id), though. We should enforce that the sessions collection is created with the expected shard key and check whether there are any other options that you can currently change when sharding the sessions collection that shouldn't be allowed.

            Assignee:
            Unassigned Unassigned
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: