Uploaded image for project: 'MongoDB Database Tools'
  1. MongoDB Database Tools
  2. TOOLS-3068

Investigate changes in PM-2689: Prevent Data Corruption Due to Direct Shard Connections

    • Type: Icon: Investigation Investigation
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      Original Downstream Change Summary

      You are impacted if your product relies on direct connections against individual Shard nodes. We are disabling direct operations against shards. Please refer to the PD for a detailed description of the scenarios which will be broken.

      Description of Linked Ticket

      Epic Summary


      This project is about restricting the operations customers are allowed to do when directly connected to the shards in a cluster and letting them know if they're doing direct operations.


      Customers connecting directly to shards can often lead to data loss. Sometimes they don't even know they're connecting directly to a shard. This can happen when they are converting from a replica set to a sharded cluster and want to lazily bounce their app over to the sharded cluster in a rolling manner. Data loss in this scenario has occurred more than once recently. As a result, customers lose confidence in our database and wonder how/why we don't have protections in place to prevent these human errors. 

      Cast of Characters


      Product Description
      Scope Document
      Technical Design Document

            Unassigned Unassigned
            backlog-server-pm Backlog - Core Eng Program Management Team
            0 Vote for this issue
            2 Start watching this issue