Add node to replica set in MMS

[Karina G]

Hi,

In an attempt to solve the issue of my nodes not replicating, I tried to remove a node from a replica set in MMS with the hope I could add it straight back in and replication would restart. Unfortunately there doesn't seem to be an obvious option to add the node back in so now I have a replica set with an arbiter and primary and a single standalone.

Can someone please help me read this back in? I hace tried running the mongo shell on the primary and running rs.add("node:port") however all I get is

{
        "down" : [
                "name:port"
        ],
        "ok" : 1
}

and nothing else seems to happen. Any help or guidance is appreciated.

Karina

[Asya Kamsky]

What version of MongoDB is this?

How did you remove the node from the replica set?

What's in the logs?

--
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/711427f2-0ca9-468a-ac8d-fb9bf6daa666%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
MongoDB World is back! June 1-2 in NYC. Use code ASYA for 25% off!

[Karina G]

Hi Asya,

Thanks for your reply, requested info:

Mongo Version: 2.6.7

Removed the node from within MMS by clicking on it and selecting remove from replica set.

Which logs? Ones on the server or ones in the website, either way can you please provide name of log you are after?

Karina

[Asya Kamsky]

Karina:

I missed that you removed the node in MMS...

Hmm.. I think I may be remembering running into some issue when I
tried removing a node from a replica set and then immediately trying
to add it back, but I can't recall the details of it right off hand.

Maybe one of the MMS Group folks will be able to clarify what might be
happening.

Asya

> --
> 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/9182bc94-0463-4e69-b9d7-177cc3b77d2c%40googlegroups.com.

[Dennis Kuczynski]

Hi Karina,

Once a member is removed from a replica set in the MMS UI, it becomes a standalone process. (As you describe)

However, there is not currently a quick UI hook to add a specific standalone process to a replica set.

You can however add a new member to the replica set, by clicking on the Replica Set item, and modifying the replica set's Member Options.

You will be able to select which server the new member ends up on, by using the dropdown above the member list item.

You may want to shutdown and unmanage the standalone process before adding the new member.  If you want the new member to use the same settings, e.g. dbPath/port as the old member, you may have to edit the new member process in the process editor screen before deploying the changes.

Let me know if that helps,

Dennis

[Karina G]

Thank you Dennis,

This method seems to have worked. However it has not resolved my original issue of the databases not replicating - I will log a separate issue for this.

Thank you for your help.

Karina