Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11864

Zone Sharding example is misleading regarding behavior on documents outside of all tag ranges

    XMLWordPrintableJSON

Details

    Description

      ----------------------------

      Original Description

      https://docs.mongodb.com/manual/core/zone-sharding/#zones

      In the example, document

      { x : 23 }

      ends up on shard "Charlie". This is indeed possible. But it is not the only possibility. My testing showed that in the case of documents not covered by any of the configured tag ranges, those documents will be balanced among all shards – those with and without a tag. So the

      { x : 23 }

      could end up on shard "Charlie". But it could end up on "Alpha" or "Beta", too. Showing it on "Charlie" incorrectly implies that it could only end up there, which is not correct.

      Documents (again, per my testing) not falling in any tag range end up on shards with and without tags, not only on shards without tag. The example should make that clear – i.e, by showing document

      { x :25 }

      on shard alpha, and explaining why that happens.
      ----------------------------

      Description

      Scope of changes (files that need work and how much)

      Impact to other docs outside of this product

      MVP (work and date?)

      Resources (e.g. Scope Docs, Invision)

      Attachments

        Activity

          People

            Unassigned Unassigned
            eric.sommer@mongodb.com Eric Sommer
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              1 year, 14 weeks, 2 days ago