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

Add logging to inform where split points are chosen in shardCollection with hashed key

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2017-01-02
    • 0

    Description

      BF-1916 is an instance where shardCollection with a hashed key fails to split any chunks. There isn't enough logging to make it clear where in the logic it decided there should be no split points, and the failure has not been reproducible.

      The logs do say "going to create 1 chunk(s) for", which indicates that no split points were provided by the time ChunkManager::createFirstChunks starts its for-loop to perform splits.

      Add some logging to pinpoint where between the shardCollection command and the createFirstChunks call the split points can fail to be created, so that if the BF ever happens again it can be fixed.

      Attachments

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: