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

MongoDB Thinks Chunk Has 1284 Petabytes in it

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.0
    • Component/s: Sharding
    • Labels:
      None
    • Sharding
    • Fully Compatible
    • ALL

      No repro, but exists in currently running system. See SO here:

      http://dba.stackexchange.com/questions/98836/mongo-shard-with-negative-average-size

      Here's output from a move shard:

      {
      	"cause" : {
      		"chunkTooBig" : true,
      		"estimatedChunkSize" : NumberLong("1284608926708044072"),
      		"ok" : 0,
      		"errmsg" : "chunk too big to move",
      		"$gleStats" : {
      			"lastOpTime" : Timestamp(0, 0),
      			"electionId" : ObjectId("553034c33e622e6efa8c0a6c")
      		}
      	},
      	"ok" : 0,
      	"errmsg" : "move failed"
      }
      

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            pat.white@synata.com Patrick White
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: