refineShardKey shouldn't update everything in a single transaction

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 3
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      Today refineShardKey updates everything in a single transaction as the title implies.

      It modifies the following in a single transaction:

      The main issue is that while the collection entry and zones can be reasonably assumed to be small the chunks themselves can be unbounded in size. That is, in a single transaction we could potentially be modifying millions of documents which is in direct contradiction of best practices.

            Assignee:
            Unassigned
            Reporter:
            Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: