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

splitChunk returns with error cause truncated

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 3.3.2
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      Example error:

      {
          "cause" : "SplitFailed: splitChunk failed - cmd: { splitChunk: \"test.user\", keyPattern: { x: 1.0 }, min: { x: MinKey }, max: { x: MaxKey }, from: \"shard0000\", splitKeys: [ { x: 0.0 } ], configdb: \"test-configRS/ren-desktop:20004,ren-desktop:20005,ren-desktop:20006\", shardVersion: [ Timestamp 1000|0, ObjectId('56cf64adedc7308da7815029') ], epoch: ObjectId('56cf64adedc7308da7815029') } result: { ok: 0.0, errmsg: \"splitChunk cannot split chunk [{ x: MinKey },{ x: MaxKey }) :: caused by :: Operation timed out, request was RemoteCommand 14 -- target:ren-desktop:20...\" }",
          "ok" : 0,
          "errmsg" : "split failed"
      }
      

      This is because BSONElement::toString has a 150 char limit for strings unless full = true. So the error message generated here needs to be shortened or use full = true:

      https://github.com/mongodb/mongo/blob/r3.3.2/src/mongo/s/chunk.cpp#L458

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: