Home PC Games Linux Windows Database Network Programming Server Mobile  
  Home \ Server \ Difference LVS three scheduling modes     - exp / imp Export Import version of the problem and the ORA-6550 error (Database)

- Android Application Development: an argument between Activity (Programming)

- Installation on the way to the root source Ubuntu Server 14.04 LTS version Odoo8.0 (Server)

- Let Linux operating system more secure (Linux)

- Based Docker build stand-alone high-availability cluster Hadoop2.7.1 Spark1.7 (Server)

- To install Ganglia (Linux)

- grep search from files and display the file name (Linux)

- Construction LVM-based raw device Oracle10g Database on Oracle Linux 5.11 (Database)

- How to create a remote (Linux)

- Setting grep Highlight Matches (Linux)

- Perl said method B if A judge (Programming)

- Oracle to use full-text indexing (Database)

- To deploy MySQL database with separate read and write OneProxy (Database)

- Use the TC flow control test under Linux (Linux)

- Linux configuration Samba server (Server)

- The Sublime Text 3 configuration file (Linux)

- RabbitMQ tutorial examples: RabbitMQ installation under Windows (Linux)

- Three easy open source firewall on the Linux platform (Linux)

- NFS installation process under the CentOS (Linux)

- Ubuntu Tutorial: How to Upgrade a New Linux Kernel 3.12.7 on Ubuntu (Linux)

  Difference LVS three scheduling modes
  Add Date : 2018-11-21      
DR: direct routing

TUN: Tunnel

Cluster node with the director must be in the same IP network;
RIP is typically a private address only for communications between each cluster node;
Director is located between the client and the real server, and handles all incoming and outgoing communication;
real server must Gateway at DIP;
Support port mapping;
real Server can use any OS;
Large-scale application scenarios, director easily become a system bottleneck;

Cluster node with the director must agree to a physical network;
RIP can use public addresses, for convenient remote management and monitoring;
director responsible for handling inbound requests only, by the director in response to heat directly to the client;
You can not point to the real server gateway DIP;
It does not support port mapping;
It does not change the destination address (because real Server has been bound to the VIP)
Rewriting request mac address of the packet (the MAC address of the machine VIP rewrites the MAC address of the real server back-end)


Cluster nodes across Internet;
RIP must be a public IP address;
dirctor only responsible for handling inbound requests, the corresponding message sent directly by the real server to the client;
real server gateway can not point to the director;
OS only supports tunnel function can be used for realserver;
It does not support port mapping;
- Linux compiler installation Redis (Database)
- CentOS7 Kubernetes used on container management (Server)
- PLSQL often lose resolution process automatically disconnect the connection (Database)
- C ++ precision performance test function (Programming)
- Computer security perimeter recommendations (Linux)
- Apache Linux firewall reverse proxy configuration (Linux)
- Oracle 11g statistics collection - collection of multi-column statistics (Database)
- Memcached distributed caching (Server)
- CentOS How to mount the hard drive (Linux)
- Video editing captions under Linux (Linux)
- Ceph Source Analysis: Network Module (Server)
- How to install Go1.5 source development environment on Mac (Server)
- MySQL flip-flop (Database)
- Use GLOBK batch command network adjustment (Linux)
- Multipath configuration under Linux (Linux)
- Linux basic introductory tutorial ---- regex basis (Linux)
- Figlet use (Linux)
- Linux port scanning (Linux)
- CentOS / Linux restart active NIC connection paths / network configure error Error Resolution (Linux)
- HBase vs Oracle (Database)
  CopyRight 2002-2020 newfreesoft.com, All Rights Reserved.