Tag Info

New answers tagged

2

MongoDB's operating documentation is usually rather thin, but they do cover a similar case. See https://docs.mongodb.org/master/release-notes/3.0-upgrade/#upgrade-a-replica-set-to-3-0. In short, yes, you can do this. You should keep a backup, though. Also, there is little reason to do it this way, since you can convert to the new storage engine after the ...


1

The next steps resolved the similar trouble: On the PRIMARY member: rs.status() { "set" : "ShardD", "date" : ISODate("2015-08-28T17:01:40.647Z"), "myState" : 1, "members" : [ { "_id" : 0, "name" : "host.example.com:27017", "health" : 1, "state" : 1, "stateStr" : ...


1

The bind_ip directive is meant to specify the IP addresses on that same system to which MongoDB listens for connections, not IP addresses from which it receives connections. Set this option to configure the mongod or mongos process to bind to and listen for connections from applications on this address. You may attach mongod or mongos instances to any ...


0

I haven't tried Humongous, but I guess there's a guide on Humongous to help you to connect to your mongod In most cases, mongod bind to localhost only, so you need to change your mongod to bind to a public ip, check here. But this will also increase security concerns. Also make sure you have set up authentication to make sure no unauthorized access is ...


0

I reread http://docs.mongodb.org/manual/tutorial/enable-authentication-without-bypass/ :) 1) I started on the C1, C2, C3: mongod --configsvr --logpath /var/log/mongodb/mongod.log --fork mongos --configdb 10.77.14.247:27019,10.77.14.248:27019,10.77.14.249:27019 --port 40000 --logpath /data/mongos.log --fork 2) I created a new user on mongos: use admin ...


0

In my experience to completely turn off failover (and remove the current primary from the pool) you need to do the following: From the current primary, use rs.remove() to remove all secondary nodes from the group. Stop mongod on the current primary. Follow the instructions here - namely delete all local.* files on the primary instance and remove any ...


1

The general principle at work here is called "service discovery". There are any number of different ways of achieving it. Here are a few: Query the EC2 APIs for the list of machines in the group at any particular time. Have the machines register themselves in DNS (via any number of means) against a common RR name; when you retrieve the records for that ...


0

It is important to establish a solid baseline prior designing your hardware. Generally expect these kind of questions to be asked by the experienced mongoDB folks before anyone can even consider answering your question. Current Application Stats (if any) Total Records to date? Starting storage estimate? Expected % growth/month? Average Document Size? ...


5

There should be no need to reinvent this wheel, it's been done plenty of times before. Depending on your OS/Distro then there should be a process supervisor you can leverage already available. Currently systemd and upstart are fairly common.



Top 50 recent answers are included