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

Log messages regarding chunks not very informative when the shard key is of type BinData

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: 2.2.4, 2.4.3
    • Fix Version/s: 2.6.4, 2.7.2
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:

      Description

      When the data type of the shard key is BinData, log messages regarding chunk limits and split keys are not very informative since BinData keys are printed in abbreviated form like:

      { _id: BinData } --> { _id: BinData }

      If, on the other hand, the type of the shard key is say a number, the log messages are useful:

      { _id: 103 } --> { _id: 206 }

      This truncation of BinData in the log messages makes it difficult to track sharding problems when BinData is used as a shard key.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: