Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion distributing storage?

Received: by 10.52.23.70 with SMTP id k6mr10575301vdf.1.1322753178094;
        Thu, 01 Dec 2011 07:26:18 -0800 (PST)
X-BeenThere: mongodb-user@googlegroups.com
Received: by 10.220.81.139 with SMTP id x11ls7040421vck.5.gmail; Thu, 01 Dec
 2011 07:26:08 -0800 (PST)
Received: by 10.52.174.114 with SMTP id br18mr10571590vdc.2.1322753168462;
        Thu, 01 Dec 2011 07:26:08 -0800 (PST)
Received: by 10.52.174.114 with SMTP id br18mr10571586vdc.2.1322753168454;
        Thu, 01 Dec 2011 07:26:08 -0800 (PST)
Return-Path: <darreng5...@gmail.com>
Received: from mail-qw0-f56.google.com (mail-qw0-f56.google.com [209.85.216.56])
        by gmr-mx.google.com with ESMTPS id g14si2498643qcy.2.2011.12.01.07.26.08
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 01 Dec 2011 07:26:08 -0800 (PST)
Received-SPF: pass (google.com: domain of darreng5...@gmail.com designates 209.85.216.56 as permitted sender) client-ip=209.85.216.56;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of darreng5...@gmail.com designates 209.85.216.56 as permitted sender) smtp.mail=darreng5...@gmail.com
Received: by qap15 with SMTP id 15so176917qap.11
        for <mongodb-user@googlegroups.com>; Thu, 01 Dec 2011 07:26:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.246.4 with SMTP id lw4mr121841qcb.6.1322753168381; Thu, 01
 Dec 2011 07:26:08 -0800 (PST)
Received: by z1g2000vbx.googlegroups.com with HTTP; Thu, 1 Dec 2011 07:26:08
 -0800 (PST)
Date: Thu, 1 Dec 2011 07:26:08 -0800 (PST)
In-Reply-To: <CANrr8GVKdiR+gn1CuQmf9oC=5O6zHBer7O1_rSMKo3o0ea0SjA@mail.gmail.com>
References: <5e82fcaf-3812-4700-b9e5-580b85762473@n35g2000yqf.googlegroups.com>
 <CANrr8GVKdiR+gn1CuQmf9oC=5O6zHBer7O1_rSMKo3o0ea0SjA@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.24)
 Gecko/20111103 Firefox/3.6.24 (.NET CLR 3.5.30729),gzip(gfe)
Message-ID: <269974da-8499-41ee-a18b-25aa9ec88ef9@z1g2000vbx.googlegroups.com>
Subject: Re: distributing storage?
From: project2501 <darreng5...@gmail.com>
To: mongodb-user <mongodb-user@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,
  Thanks for the tip. If they are randomly inserted into shards, and
evenly distributed.
Then at query time, the id's are returned with no additional penalty,
yes? Because
all the shards got the query.

Is it then possible to know what shard the result id came from and
retrieve it from only that shard?

thanks.

On Dec 1, 10:22=A0am, Sergei Tulentsev <sergei.tulent...@gmail.com>
wrote:
> If you're updating a document, this write will go to its shard. If you're
> inserting a new document, it will go to a shard where its chunk lives. If
> you want random distribution of new documents, use random shard key, like
> md5 of something.
> But there are some serious drawbacks in this approach. For example, a
> simple retrieval by _id will go to all shard (unless you specify shard ke=
y,
> which you will have to calculate again).
>
>
>
> On Thu, Dec 1, 2011 at 7:06 PM, project2501 <darreng5...@gmail.com> wrote=
:
> > Hi,
> > =A0I know about mongodb's auto-scaling/sharding and that it is
> > triggered by storage limits in size.
> > But can I distribute my document writes evenly across a cluster? In
> > other words, I want mongos to do something like a round-robin or some
> > other algorithm to distribute writes across the cluster as they
> > arrive.
>
> > Is it possible?
>
> > thanks.
>
> > --
> > You received this message because you are subscribed to the Google Grou=
ps
> > "mongodb-user" group.
> > To post to this group, send email to mongodb-user@googlegroups.com.
> > To unsubscribe from this group, send email to
> > mongodb-user+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/mongodb-user?hl=3Den.
>
> --
> Best regards,
> Sergei Tulentsev