Received: by 10.50.170.72 with SMTP id ak8mr5983845igc.0.1349185474326;
        Tue, 02 Oct 2012 06:44:34 -0700 (PDT)
X-BeenThere: mongodb-user@googlegroups.com
Received: by 10.50.36.129 with SMTP id q1ls915906igj.0.gmail; Tue, 02 Oct 2012
 06:44:25 -0700 (PDT)
Received: by 10.50.178.38 with SMTP id cv6mr5977530igc.2.1349185465168;
        Tue, 02 Oct 2012 06:44:25 -0700 (PDT)
Received: by 10.50.178.38 with SMTP id cv6mr5977529igc.2.1349185465154;
        Tue, 02 Oct 2012 06:44:25 -0700 (PDT)
Return-Path: <mia...@gmail.com>
Received: from mail-ie0-f177.google.com (mail-ie0-f177.google.com [209.85.223.177])
        by gmr-mx.google.com with ESMTPS id rf8si157847igb.2.2012.10.02.06.44.25
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 02 Oct 2012 06:44:25 -0700 (PDT)
Received-SPF: pass (google.com: domain of mia...@gmail.com designates 209.85.223.177 as permitted sender) client-ip=209.85.223.177;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of mia...@gmail.com designates 209.85.223.177 as permitted sender) smtp.mail=mia...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-ie0-f177.google.com with SMTP id e14so17525002iej.8
        for <mongodb-user@googlegroups.com>; Tue, 02 Oct 2012 06:44:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=UpIQK5GASeTPX+QLKoy9JZg6QMjFHIWa8lV0ex5ytaU=;
        b=znxCM12ww1WqVtiF5sehTn+HPgUyGwdWLXpCRwxLjv0QZOp18pJISI00TgZVnzvWXP
         16RP7sIkoPYBlNk2nP0rGBjDpj5vNMt1Upetsnuv+OfNfLfDD74kiz3bW4NODyIpWrvi
         Rrfi6UCWv/vNhSOhPCeQBm1fhPZUnLiBtKytX/1DsujP5+SB2vcrugIcFS5pVX5zfQ/f
         1iyZk2nUxglZzNdF8ve3y9rkVuqa+ZRlFryyQ0l9PLiZo5vdzeDm1yK7RjnpMFpjEKM3
         L8XObUyDYnNX/4MFzAfxjzfg7McxzdUYmh6/PBWvNmMFp/Pl30K2Op2/gyN/OO2Y5pNb
         YSEw==
MIME-Version: 1.0
Received: by 10.50.190.163 with SMTP id gr3mr8785118igc.69.1349185464251; Tue,
 02 Oct 2012 06:44:24 -0700 (PDT)
Received: by 10.64.170.136 with HTTP; Tue, 2 Oct 2012 06:44:24 -0700 (PDT)
In-Reply-To: <686be91b-9d76-4513-8709-d977e98646a2@googlegroups.com>
References: <686be91b-9d76-4513-8709-d977e98646a2@googlegroups.com>
Date: Tue, 2 Oct 2012 10:44:24 -0300
Message-ID: <CAMzU8N=4Gt0n6v_RZuye+r1_u1WUZq9Xeu3MEW0Y-2gF+Wh...@mail.gmail.com>
Subject: Re: [mongodb-user] Moving a collection to a new database (v2.2)
From: Luciano Issoe <mia...@gmail.com>
To: mongodb-user@googlegroups.com
Content-Type: multipart/alternative; boundary=f46d044788175535eb04cb13b837

--f46d044788175535eb04cb13b837
Content-Type: text/plain; charset=ISO-8859-1

Did you consider upgrading the entire cluster?


On Fri, Sep 28, 2012 at 4:59 PM, Chris Wilcox <ckwil...@gmail.com> wrote:

> To take advantage of the improved concurrency in Mongodb 2.2--namely
> database level locking--we would like to move a sharded collection to a new
> database.
>
> I have been unable to find any documentation which will help with this
> particular scenario.
>
> I know I cant just "rename" this sharded collection:
> https://groups.google.com/d/topic/mongodb-user/lajAcp3HkZ4/discussion
>
> The only thing I can think of is mongodump *the entire* collection and
> mongorestore into a new database. What are my other options?
>
> Cheers!
>
> --
> You received this message because you are subscribed to the Google
> Groups "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
> See also the IRC channel -- freenode.net#mongodb
>

--f46d044788175535eb04cb13b837
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Did you consider upgrading the entire cluster? <br><br><br><div class=3D"gm=
ail_quote">On Fri, Sep 28, 2012 at 4:59 PM, Chris Wilcox <span dir=3D"ltr">=
&lt;<a href=3D"mailto:ckwil...@gmail.com" target=3D"_blank">ckwilcox@gmail.=
com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">To take advantage of the improved concurrenc=
y in Mongodb 2.2--namely database level locking--we would like to move a sh=
arded collection to a new database.<div>
<br></div><div>I have been unable to find any documentation which will help=
 with this particular scenario.=A0</div><div><br></div><div>I know I cant j=
ust &quot;rename&quot; this sharded collection: <a href=3D"https://groups.g=
oogle.com/d/topic/mongodb-user/lajAcp3HkZ4/discussion" target=3D"_blank">ht=
tps://groups.google.com/d/topic/mongodb-user/lajAcp3HkZ4/discussion</a></di=
v>
<div><br></div><div>The only thing I can think of is mongodump *the entire*=
 collection and mongorestore into a new database.=A0What are my other optio=
ns?</div><div><br></div><div>Cheers!</div><span class=3D"HOEnZb"><font colo=
r=3D"#888888">

<p></p>

-- <br>
You received this message because you are subscribed to the Google<br>
Groups &quot;mongodb-user&quot; group.<br>
To post to this group, send email to <a href=3D"mailto:mongodb-user@googleg=
roups.com" target=3D"_blank">mongodb-user@googlegroups.com</a><br>
To unsubscribe from this group, send email to<br>
<a href=3D"mailto:mongodb-user%2Bunsubscribe@googlegroups.com" target=3D"_b=
lank">mongodb-user+unsubscribe@googlegroups.com</a><br>
See also the IRC channel -- <a href=3D"http://freenode.net#mongodb" target=
=3D"_blank">freenode.net#mongodb</a><br>
</font></span></blockquote></div><br>

--f46d044788175535eb04cb13b837--