Home PC Games Linux Windows Database Network Programming Server Mobile  
           
  Home \ Database \ Understanding and Memcached MongoDB arbitration node, Zookeeper, Redis Recovery Programme Thoughts     - Golang environment configuration recommendations (Linux)

- Java reflection mechanism explained in detail and Method.invoke explanation (Programming)

- Distributed transaction management Spring declarative transactions (Programming)

- According to the national position on how to block traffic in Linux (Server)

- CentOS 7 hard disk expansion toss record (Linux)

- Fedora 22 install Adobe Flash Player (Linux)

- Setting Linux desktop environment, achieve HiDPI display support (Linux)

- Oracle 11g 10g induced into error (Database)

- Build Python3.4 + PyQt5.5.1 + Eric6.1.1 development platform under Mac OS X 10.11.1 (Server)

- Mac OS X system setup Google Go language development environment configuration tool Sublime Text 2 (Linux)

- RPM package creation Getting Started (Linux)

- Linux vi command list (Linux)

- Android Studio Getting Started Hello World (Programming)

- NaSC using simple mathematical operations on Ubuntu and Elementary OS (Linux)

- Command-line based tools for better alternatives (Linux)

- Diagnose and resolve the SSH connection slow (Linux)

- Linux environment has been running Tomcat how to deploy the new Tomcat (Server)

- Ambari and Hadoop configuration, management and monitoring of the project Getting (Server)

- Oracle 11R2 Grid Infrastructure execute root.sh script rootcrs.pl execution failed treatment (Database)

- Swift 2.0 brief (Linux)

 
         
  Understanding and Memcached MongoDB arbitration node, Zookeeper, Redis Recovery Programme Thoughts
     
  Add Date : 2018-11-21      
         
         
         
  When the replica set during deployment we'll add one or more nodes of arbitration, the arbitration node is not used for backing up data, since its mandate responsibilities is responsible for electing the master node, so not too high demands on the hardware, it can be deployed on a separate server on the server may be a server monitor can also be deployed on a virtual machine, but one thing must not arbitration node backup data. Arbitration node points and annotations can participate in the elections, the election of each object is a non-voting member, is the need to back up data from the node.

It reminds me of a previous understanding had zookeeper cluster election program, it is different and MongoDB.

ZooKeeper uses election algorithm called the Leader election. In the process of running the entire cluster, only one Leader, the other is Follower, if ZooKeeper cluster running Leader is a problem, the system will use the algorithm to re-elect a Leader. Thus, between the various nodes connected to each other to be able to guarantee, you must configure the mapping described above.

ZooKeeper cluster startup time, will first elect a Leader, the Leader election process, to meet a certain node election count can become Leader.

For memcached does not provide a distributed approach, we can use a proxy server to implement a distributed deployment. And Magent memcached is a proxy server, but it does not exist any leader, secondary, all commands are magent entrance proxy server, when a node machine when done, but could not find the requested data, it will be from the backup node Obtain. When we make available through the zookeeper to manage memcached distributed clusters.

For after redis when set up slave servers, slave and master establishes a connection, then send sync commands. Whether it is to re-establish synchronization even connected for the first time or after the connection is disconnected, master will start a background process to save database snapshot to a file, and master the main process will begin collecting new write command and cached. After the completion of background process to write the file, master file is sent to the slave, slave to save the file to disk, and then loaded into memory to restore the database snapshot on slave. Then master will put forward the cache command to the slave. And the subsequent write command received will be sent to the master slave began to build the connection. Command from master to slave synchronization of data and commands sent from the client to use the same protocol format. slave can be automatically re-establish the connection when the master and the slave disconnected. If you receive more than one slave master simultaneously sent to the synchronous connection commands will use to start a process to write database mirroring, and then sent to all slave. For when the master fails, we can restore persistent data, but it fails to salve and master will then reconnect all written within the slave from the snapshot seen this recovery must be very slow.
     
         
         
         
  More:      
 
- Oracle data files deleted recover after physical (Database)
- CentOS 7 open ports (Linux)
- MySQL 5.7.9 source compiler installation instructions (Database)
- Ordinary users how to use the firewall software (Linux)
- Hibernate Search 5.5 in the search results sorted (Linux)
- Manage SQL Server services login (start) account and password (Database)
- Manually generate AWR reports (Database)
- Installation under Linux Mint system guidelines for Gtk (Linux)
- Linux installed PCRE (Linux)
- Ubuntu Linux to create and increase the Swap partition tutorial (Linux)
- Oracle 11g forget approach SYS and SYSTEM password (Database)
- Ubuntu program using the Sound Recorder (Linux)
- Yii PHP Framework Getting Started tutorial (Linux)
- RAID configuration and management under linux (Server)
- GRUB2 boot Ubuntu Manual (Linux)
- MySQL view (Database)
- RedHat / CentOS ext4 partition can not be formatted large supplementary ext4 formatting (Linux)
- Postgres-X2 deployment steps (Database)
- Oracle TAF Analysis (Database)
- CentOS install Java 1.8 (Linux)
     
           
     
  CopyRight 2002-2022 newfreesoft.com, All Rights Reserved.