• Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      Handling autoCompact in stopReplicaSetWrites requires a lot of complexity, we need to remember the current state, disable it with retries (because WT can fail), handle rollbacks and reconciliation, consider the case where autoCompact is re-set with bypass, etc.

      autoCompact should increase disk usage very slightly and it's probably not worth supporting it. Analyze the real usage on the fleet by looking at metrics, how often we stop writes on clusters that use it, and consider removing all complexity related to it.

            Assignee:
            Unassigned
            Reporter:
            Daniel Gomez Ferro
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: