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

Shard maxSize should be more accurate wrt space used/free

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding

      Currently this value is taken from the server mapped memory number and results in no chunks being moved to the shard even if there is room in existing files (from deleted extents or docs).

      Taking the sum of each databases datasize would be a better I believe.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            scotthernandez Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: