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

detect data inserted directly into a shard server incorrectly

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Sharding
    • Labels:
      None

      Description

      When changing from a non-sharded to a sharded deployment, it is easy to forget
      to update all application components to connect through mongos instead of
      connecting to a replica set. If this conversion is missed, it is possible for
      an application to insert data into a sharded collection directly, bypassing
      mongos. This can result in data being inserted into the incorrect shard.
      Such data appears to disappear when sought through mongos: mongos will route
      queries to the appropriate shard, and the data is not found there.

      Shard servers are aware they are part of a sharded setup because of the
      shardsvr startup flag. Therefore, they should be able to verify inserted data
      is within the expected shard chunk key ranges for themselves, and complain
      otherwise.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated: