--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user...@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CALQwOA2%3D4oB6MmtD788%2B6w4m-QSb4%3Dt9z3%2BJKOTVc8HLmkGsjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CAOe6dJAfebL2AcW5C%3DoPS%3D5Q-prDPqdmheRpTXGgBi%3DwOh%2BKDg%40mail.gmail.com.
No, absolutely not. Insertion goes directly into shard that owns that chunk.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CALQwOA1tWH0kO3q18xP7G64toqkm1p3k2NYgE%2B_3K5yrD6ffVg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CAOe6dJAL%3DVCyP%2BZOBJ0ihkFigT0rzGLFEbGHjAShCbZa75HE5Q%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CALQwOA0boQf%2BqNyvW5ybSkAVWSPqRUNk7Rffsy097vManSCtTw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CAOe6dJBYYBHhbmWYQeD7iczA6yCpkBVg7qJj%3DzdRPyb-a5DeFQ%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+unsubscribe@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CALQwOA2%3D4oB6MmtD788%2B6w4m-QSb4%3Dt9z3%2BJKOTVc8HLmkGsjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+unsubscribe@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CAOe6dJAfebL2AcW5C%3DoPS%3D5Q-prDPqdmheRpTXGgBi%3DwOh%2BKDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+unsubscribe@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CALQwOA1tWH0kO3q18xP7G64toqkm1p3k2NYgE%2B_3K5yrD6ffVg%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+unsubscribe@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CAOe6dJAL%3DVCyP%2BZOBJ0ihkFigT0rzGLFEbGHjAShCbZa75HE5Q%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+unsubscribe@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CALQwOA0boQf%2BqNyvW5ybSkAVWSPqRUNk7Rffsy097vManSCtTw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/fa75a5ab-77a9-4f94-9cc1-12984a397709%40googlegroups.com.
Hello,
I am using the "split" command with the "moveChunk" to move the splitted chunk to the shard where it should stay.Is this the right approach?
Also, there is some overhead for big chuncks? I am creating one big chunk (1Gb) for each shards (total of 4).
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/71a4a409-134e-4426-9592-810ca7b3ad19%40googlegroups.com.
moveChunk returns the following error message if another metadata operation is in progress on thechunks collection:
errmsg: "The collection's metadata lock is already taken."
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/811da30c-cda6-462d-993b-3505794e2abd%40googlegroups.com.
2014-07-11T21:33:23.139+0200 [conn16] ChunkManager: time to load chunks for work_db.regions.hg19.e99.chrX: 0ms sequenceNumber: 40968386 version: 2|3||53bfe2f47288ce5c348751a0 based on: (empty)
2014-07-11T21:33:23.139+0200 [conn16] ChunkManager: time to load chunks for work_db.regions.hg19.e99.chrY: 0ms sequenceNumber: 40968387 version: 2|1||53bfe3017288ce5c348751af based on: (empty)
2014-07-11T21:33:23.140+0200 [conn16] ChunkManager: time to load chunks for work_db.regions.hg19.e357.chr12: 0ms sequenceNumber: 40968388 version: 2|1||53c03be47288ce5c348799a9 based on: 2|1||53c03be47288ce5c348799a9
2014-07-11T21:33:23.140+0200 [conn16] warning: chunk manager reload forced for collection 'work_db.regions.hg19.e357.chr12', config version is 2|1||53c03be47288ce5c348799a9
The problem is that each sharded collection, I have a list of this message and I see that the insertions halt for a few seconds.
The command that I am executing is:
{ split: "work_db.regions.hg19. e357.chr12", middle: { S: 40597605 } }
Does the split command force the chunk manager reload its data?
How can I improve it?
Thank you,
Felipe Albrecht