Have you "presplit" and balanced the collection?
From your description it sounds Like all of the writes are going to the
If so then pre-splitting will help get the cluster to a level state and
After the splits you will want to "pre-balance" the chunks to avoid issues
If you are careful about picking split points you can initially make as
Try to estimate the number of chunks you will have in steady state (data
On Friday, October 12, 2012 2:01:09 PM UTC-4, Merl wrote:
> Any ideas of what I should be looking for as our bottlekneck?
>> What are you connecting to from your application? Mongos
>> When you say, "our cluster loads an unreal amount of data", what exactly
>> Where does the data come from? Is it evenly spread across your cluster?
>> When you say, "ram fills up, the chunks starts building up" - RAM on
>> So in summary:
>> Node 1: Mongod, Mongos, App which loads the data
>> Each Node: 96GB Ram, 24 Hyperthreaded Cores, 6 - 300GB SAS Drives 16MB
>>> To isolate what might be causing your issues:
>>> What are you connecting to from your application? Is it a mongos, or is
>>> On Thursday, October 11, 2012 10:42:34 AM UTC-4, Merl wrote:
>>>> It is 2 random 8 character strings as a compound as a compound shard
>>>> On Thu, Oct 11, 2012 at 10:27 AM, Sam Helman <sam.h...@10gen.com>wrote:
>>>>> I do not know of any issues with Morphia, what is your current shard
>>>>> On Thursday, October 11, 2012 9:31:41 AM UTC-4, Merl wrote:
>>>>>> I am curious. Is morphia still recommended to be used with Mongo?
>>>>> To unsubscribe from this group, send email to
>>>>> See also the IRC channel -- freenode.net#mongodb
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.