Curious to know why deleting the chunk's existence is bad. The chunk is
gone.
> Change owners, deleting the chunks would be bad.
> On Wed, Jan 5, 2011 at 5:45 PM, Ted <underhi...@gmail.com> wrote:
> > I would like to have a working cluster with 2 servers. No worries about
> the
> > lost chunks from the down server since this is a test system (I was
> bummed
> > because the db was almost at a 1B rows).
> > Do I change owners or just delete the chunk's existence on the config
> > server?
> > On Wed, Jan 5, 2011 at 5:35 PM, Eliot Horowitz <eliothorow...@gmail.com>
> > wrote:
> >> What state do you want to end up?
> >> You can do some hackery on the config db if you need?
> >> i.e. shutdown all shards + mongos
> >> remove that shard from the shards collection
> >> change the owner of all chunks that were on that shard somewhere
> else
> >> obviously on a live system that would cause havoc, but should work
> >> On Wed, Jan 5, 2011 at 2:41 PM, Ted <underhi...@gmail.com> wrote:
> >> > I read through the thread a little too quick. What should I do if I
> >> > don't
> >> > have a replacement server?
> >> > On Wed, Jan 5, 2011 at 2:22 PM, Alvin Richards <al...@10gen.com>
> wrote:
> >> >> Yes, this is the best way to deal with this.
> >> >> -Alvin
> >> >> On Jan 5, 10:47 am, Ted <underhi...@gmail.com> wrote:
> >> >> > Hi,
> >> >> > I have a test cluster running 1.6.5 with 3 servers. One of the
> shard
> >> >> > servers died with no chance of recovery.
> >> >> > Is this post (http://groups.google.com/group/mongodb-user/
> browse_thread/thread/f76f1d8504101243/59633b2d68f6db1d?lnk=gst&q=failed
> >> >> > +shard+server#59633b2d68f6db1d) the best way to handle this
> >> >> > situation?
> >> >> > I just want to get the cluster going again and ignore the lost
> data.
> >> >> > Thanks.
> >> >> --
> >> >> 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<mongodb-user%2Bunsubscribe@google groups.com>
> .
> >> >> For more options, visit this group at
> >> >> http://groups.google.com/group/mongodb-user?hl=en.
> >> > --
> >> > 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<mongodb-user%2Bunsubscribe@google groups.com>
> .
> >> > For more options, visit this group at
> >> > http://groups.google.com/group/mongodb-user?hl=en.
> >> --
> >> 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<mongodb-user%2Bunsubscribe@google groups.com>
> .
> >> For more options, visit this group at
> >> http://groups.google.com/group/mongodb-user?hl=en.
> > --
> > 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<mongodb-user%2Bunsubscribe@google groups.com>
> .
> > For more options, visit this group at
> > http://groups.google.com/group/mongodb-user?hl=en.
> --
> 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<mongodb-user%2Bunsubscribe@google groups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/mongodb-user?hl=en.