Adapt sessions collection balacing policy to data-size aware balancing

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.0.3, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v6.0
    • Sharding EMEA 2022-05-30, Sharding EMEA 2022-06-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The sessions collection is sharded in order to spread sessions info across different nodes to avoid bottlenecks.
      Sessions load distribution has always happened by balancing the number of chunks across shards; with the introduction of data-size aware balancing, we should find a way to spread documents across shards considering that they are very small (~150/200 bytes in average) and their cumulative size is often much less than the default max chunk size (meaning that if balancing would happen on data size, nothing would be considered eligible to move).

            Assignee:
            Paolo Polato
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: