1

I have a sharded cluster with 4 shards, 3 config databases. My problem is when I do my inserts only one shard gets filled. Can anyone please explain to me why this is happening. My first thought was that it has something to do with the shard-key but i tried a few and nothing changed.

mongos> db.flight.stats()
{
    "sharded" : true,
    "systemFlags" : 1,
    "userFlags" : 1,
    "ns" : "flights.flight",
    "count" : 2874004,
    "numExtents" : 17,
    "size" : 689760960,
    "storageSize" : 857440256,
    "totalIndexSize" : 211537648,
    "indexSizes" : {
            "_id_" : 93255456,
            "departureAirport_1" : 118282192
    },
    "avgObjSize" : 240,
    "nindexes" : 2,
    "nchunks" : 20,
    "shards" : {
        "shard0002" : {
                    "ns" : "flights.flight",
                    "count" : 2874004,
                    "size" : 689760960,
                    "avgObjSize" : 240,
                    "storageSize" : 857440256,
                    "numExtents" : 17,
                    "nindexes" : 2,
                    "lastExtentSize" : 227803136,
                    "paddingFactor" : 1,
                    "systemFlags" : 1,
                    "userFlags" : 1,
                    "totalIndexSize" : 211537648,
                    "indexSizes" : {
                            "_id_" : 93255456,
                            "departureAirport_1" : 118282192
                    },
                    "ok" : 1
            }
    },
    "ok" : 1
}

Sharding status information:

mongos> sh.status()

sharding version: {
    "_id" : 1,
    "version" : 4,
    "minCompatibleVersion" : 4,
    "currentVersion" : 5,
    "clusterId" : ObjectId("538c20fdbf2687fbbc582642")
}
shards:
    {  "_id" : "shard0000",  "host" : "cs-mongo-shard-1-east-t:10001" }
    {  "_id" : "shard0001",  "host" : "cs-mongo-shard-2-east-t:10001" }
    {  "_id" : "shard0002",  "host" : "10.1.10.15:10001" }
databases:
    {  "_id" : "admin",  "partitioned" : false,  "primary" : "config" }
    {  "_id" : "flights",  "partitioned" : true,  "primary" : "shard0002" }
        flights.flight
            shard key: {
    "departureAirport" : 1,
    "arrivalAirport" : 1,
    "departureDate" : 1,
    "availability" : 1
}
        chunks:
            shard0002    1
    {
    "departureAirport" : { "$minKey" : 1 },
    "arrivalAirport" : { "$minKey" : 1 },
    "departureDate" : { "$minKey" : 1 },
    "availability" : { "$minKey" : 1 }
} -->> {
    "departureAirport" : { "$maxKey" : 1 },
    "arrivalAirport" : { "$maxKey" : 1 },
    "departureDate" : { "$maxKey" : 1 },
    "availability" : { "$maxKey" : 1 }
} on : shard0002 Timestamp(1, 0) 
  • 2
    I don't think you understand what sharding is & is used for. en.wikipedia.org/wiki/Shard_(database_architecture) – Philᵀᴹ May 28 '14 at 10:02
  • wow "very constructive" – aQuip May 28 '14 at 13:08
  • have you actually sharded the collection? If not it will just stay on one shard. Please post the output of sh.status() – Adam C May 29 '14 at 9:17
  • @AdamC I postet the output of sh.status() for you. – aQuip Jun 2 '14 at 7:07
1

OK, flights.flight is sharded but basically only has one chunk so far, and hence all current data is on one shard and so all writes can only go to one shard - you will need more before the collection can be balanced across multiple shards. Unless you pre-split (something like this) or use a hashed shard key (which you are not) then the mongos process is what is responsible for automatically splitting the chunks.

It will attempt the first split after it has seen writes of approximately 20% of the max chunk size (default is 64MiB, so 20% is ~13MiB). It looks like this has not yet happened, or has failed for some reason in your case.

It should be noted that although the mongos will track all the writes, it will lose its "history" if restarted. It should also be noted that the config servers must be up and working for any splits to happen. Check the mongos logs for any evidence of split failures or similar.

If you want to kick start things manually, just pick two (or more) reasonable split points and use the splitAt() command to break up your current single chunk. You can then wait for the balancer to move things, or you can move them manually with the moveChunk() command. You can find examples of this in the answer to the question I linked above.

0

I was having a similar experience, i was inserting 1.4 billion documents into a sharded collection, but all documents would stay on one shard, then i read that the insertion has to be done on the Mongos (route) server and it would take care of dividing the documents into chunks and sending to the separated shards as per the key scheme.

here is more information on it here: dividing documents onto shards

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.