azure availability set

Set up the high-availability cluster environment of RabbitMq in CentOS, and set up centosrabbitmqPreparations 1: Prepare two or more servers with the rabbitmq-server service installed. I have prepared the following two servers: 192.168.40.130 rabbitmq01192.168.40.131 rabbitmq022. Make sure that the firewall is disabled. 3. Official website references Http://www.r

I. Setting up a virtual directory in a Web applicationIi. in the virtual directory, a file, Web. config, reads as follows:　　XML version= "1.0"?> Configuration> system.webserver> handlers> Clear/> Addname= "Staticfile"Path="*"verb="*"Modules= "Staticfilemodule,defaultdocumentmodule,directorylistingmodule"ResourceType= "either"requireaccess= "Read" /> handlers> system.webserver>Configuration> Ways to set up a

In this example, I will configure a cloud service Travelweb, which has two VMs, which together provide HTTP services1. Create the first VM TRAVELWEB01, specify the cloud service name as Travelweb when you create it, add an HTTP endpoint2. Create a second VM TRAVELWEB02, using the existing cloud service TravelwebAt this point, both VMs are under the same cloud service and TRAVELWEB02 cannot use public ports 80 and 223. Modify the TRAVELWEB01 endpoint to create a load balancer

Set up nginx high-availability server Load balancer cluster instances I. nginx high-availability cluster topology architecture Node1: 17216.100.67Node2: 170.16.100.68VIP: 172.16.100.89RS1: 172.16.100.6Rs2: 172.16.100.69 Note: The Kernel Parameters arp_ignore and arp_announce of all Rs in nginx high-availability cluste

Tags: file oplog start pen replica ini map technology share modMongoDB Replica Set A replica set (Replica sets) is an additional copy of the data that is the process of synchronizing data across multiple servers, providing redundant backups and increasing the availability of data, which can be used to recover hardware failures and interrupted services.

Tags: des class blog Code http TarHttp://www.lanceyan.com/tech/mongodb_repset2.htmlIn the previous article, "Building a high-availability MongoDB cluster (ii)-Replica set" describes the configuration of the replica set, which delves into the internal mechanisms of the replica set. Take a look at the problem with the re

({listshards:1})Activates the Shard configuration. UseSh.enablesharding ("library name");Add a library and shard it.UseSh.shardcollection ("library name. Collection name", {"_id": "Hashed"});Create the corresponding table (collection) and hash The Shard.Switch to a new library using the use library nameUseDb.createuser ({User: "xxx", pwd: "xxx", Roles:[{role: "Dbowner", DB: "Library name"}]});Create the corresponding user.Verifying routes1, use the name of the library (the new library above);2.

Building a high-availability MongoDB cluster (iii)--deep inside the replica set internal mechanismIn the previous article, "Building a high-availability MongoDB cluster (ii)-Replica set" describes the configuration of the replica set, which delves into the internal mechanism