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

Abort chunk migration after cloning more data than expected

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL

      In the cloning phase, we should define some kind of limit (probably based on the max chunk size) that once it's reached migrations are aborted. This scenario might happen if the chunk being migrated is also receiving a lot of data or if the balancer wrongly decided to move a chunk whose real size was much bigger than the approximated size. Note that the approximated size of a chunk is computed as NumberOfDocsInTheChunk * averageSizePerDoc.

      Note that those chunks should be marked as jumbo, otherwise the balancer will deterministically try to move them again.

            Assignee:
            Unassigned Unassigned
            Reporter:
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: