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

Add more details on why a shard is 'unavailable' for balancing

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • 2.4.6, 2.5.0
    • 2.3.1
    • Sharding
    • ALL

    Description

      This is the current code in DistributionStatus::getBestReceieverShard @ balancer_policy.cpp:

      if ( i->second.isSizeMaxed() || i->second.isDraining() || i->second.hasOpsQueued() ) {
        LOG(1) << i->first << " is unavailable" << endl;
        continue;
      }

      It would probably be nice if we split these up and display a different log message for each case.

      Attachments

        Activity

          People

            randolph@mongodb.com Randolph Tan
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: