Home PC Games Linux Windows Database Network Programming Server Mobile  
           
  Home \ Database \ Understanding and Memcached MongoDB arbitration node, Zookeeper, Redis Recovery Programme Thoughts     - Ubuntu Tutorial: How to Upgrade a New Linux Kernel 3.12.7 on Ubuntu (Linux)

- 25 Git Advanced Skills (Linux)

- Python substring format (Programming)

- MongoDB in bulk timestamp change the date format (Database)

- PL / SQL -> UTL_FILE use presentation package (Database)

- Google open source TCP team repaired the Linux kernel TCP flaw (Linux)

- grep command output highlighted word (Linux)

- Testing Oracle 11g RMAN replicate database (Database)

- Ubuntu amend resolv.conf restart failure problem (Linux)

- Stunning exclamation point at the Linux command line (Linux)

- Valgrind * not * leak check tool (Linux)

- Character Encoding notes: ASCII, Unicode and UTF-8 (Linux)

- zBackup: A versatile tool to remove duplicate backup (Linux)

- On Android running ClojureScript (Linux)

- Java concurrent programming combat (using synchronized synchronization method) (Programming)

- Linux disk virtualization (Linux)

- Efficient Linux Shell - Shell special characters Summary (Linux)

- To configure Samba to share files with Windows under CentOS (Linux)

- How nodeclub constructed Docker image (Server)

- Shared directory settings between Linux and Linux (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:      
 
- Graphical interface for the CentOS 6.4 installed and connected by remote VNC (Linux)
- How to modify the SQL Server auto-increment value and the corresponding solution (Database)
- CentOS 6.5 installation configuration DRBD (Server)
- Vi editor Introduction (Linux)
- Java interface (Programming)
- Android development, may cause a memory leak problem (Programming)
- The YUM package management under Linux (Linux)
- Upgrade Goldengate 11.1.1.1.2 to 11.2.1.0.1 (Database)
- Ubuntu Tutorial: E: Failed to get lock / var / lib / apt / lists / lock - open (Linux)
- VirtualBox 4.3 Can not open a new task for a virtual computer solution (Linux)
- To teach you how to safely send mail (Linux)
- To install and use Docker under linux (Server)
- CentOS terminal display Chinese (Linux)
- Asynchronous JavaScript loading (Programming)
- wget command Walkthrough (Linux)
- Oracle 12CIN-memory in table spaces (Database)
- The maximum subsequence algorithm and optimization problems (Programming)
- Installation Mate Desktop in FreeBSD 10.1 (Linux)
- LNMP summary of the issues common 502 Bad Gateway (Server)
- HA-Federation-HDFS + Yarn cluster deployment (Server)
     
           
     
  CopyRight 2002-2022 newfreesoft.com, All Rights Reserved.