kubernetes replica set

1. Replica setThe master-slave deployment of MongoDB is commonly used in the form of a replica set (replica set). Replica set is a set of mu

Next blog post:Http://www.cnblogs.com/xiaoit/p/4479066.html1: First create 3 virtual machines as configuration environmentip1:192.168.91.128ip2:192.168.91.129ip3:192.168.91.1302: Download MongoDB 2.6 versionHttps://fastdl.mongodb.org/win32/mongodb-win32-x86_64-2008plus-2.6.9.zip3: UnzipTAR-ZXVF Mongodb-linux-x86_64-2.6.9.zipMV mongodb-linux-x86_64-2.6.9 MongoDB　　4: Create data directory and log directory and conf configuration file in MongoDB directoryBoth data and log directories are guaranteed

mongodump.log Step 3: Restore the database on the new instance Mongorestore must be run when mongod is not started. It writes directly to the file. mongorestore --host=192.168.11.2:27017 --oplogReplay --dbpath /data/var/lib/mongodb --directoryperdb /nfspool/mongodata > mongorestore.log 2>1 You can view the log data in real time and observe the recovery progress. tail –f mongorestore.log Step 4: rebuild the oplog on the new instance 1. view the maintenance window and oplog size of the

Com.mongodb.connection.BaseCluster.createTimeoutException ( basecluster.java:377) at Com.mongodb.connection.BaseCluster.selectServer (basecluster.java:104) at Com.mongodb.bind Ing. Clusterbinding$clusterbindingconnectionsource. One of the words is that {address=127.0.0.1:27017, type=replica_set_secondary, roundtriptime=1.3 MS, state=connected} It means 127.0.0.1:27017. This server is a Secondary,mongo driver that cannot write data to the secondary node, suspected MONGO primary and secondary s

() > Db.createcollection ("oplog.rs", {"capped": true, "size": 23 * 1024 * 1 024 * 1024}) or > Db.runcommand ({create: "oplog.rs", Capped:true, Size: (23 * 1024 * 1024 * 1024)})Step five: Restore Oplog on a new instanceThis oplog is an exported Oplog.bson when mongodump.Mongorestore-d local-c Oplog.rs/nfspool/mongodata/oplog.bsonStep Six: Start a new instance with a replica setThe new instance configuration and the source

Mongodb3.0.5 replica set setup and spring and Java connection replica set configuration details First, the basic environment: mongdb3.0.5 DatabaseSpring-data-mongodb-1.7.2.jarMongo-java-driver-3.0.2.jarlinux-redhat6.3Tomcat7 Second, build MongoDB replica

This is a document written last year, recently found that there is no hair, so now make up, I hope to be helpful to some friends. Because there was no screenshot at the time, it might seem monotonous here. first, the basic environment: mongdb3.0.5 Database Spring-data-mongodb-1.7.2.jar Mongo-java-driver-3.0.2.jar linux-redhat6.3 Tomcat7 Second, build MongoDB replica set: 1. Install MongoDB on three Linux

1: Replica Set configuration reference this blog:Http://www.cnblogs.com/xiaoit/p/4478951.html2: Authentication of replica setSuppose there are two machines that have been configured with a replica set (the crime of replica

--fork--port 28014--dbpath/data/set/r4--logpath=/data/set/log/ R4.log--logappend--fastsync5.rs.add ("localhost:27017")6. Delete the node:Execute Rs.remove ("Ip:port") above the master nodeThe secondary node in the replica set is not readable by default. in applications where there is less write-read, the

Tags: replica set replica set for MongoDB cluster construction1. Environment:Open four MongoDB instances on a single server to implement the cluster setup of MongoDB's replica set replica