Introduction to the Load Balancer
In a cluster environment, requests from a client must be sent to the node which becomes newly active after a failover. LifeKeeper normally handles routing by using address resolution protocol (ARP). However, since the routing by ARP does not work in the Google Cloud VPC network environment, the requests from the client need to be controlled by introducing the load balancer.
- Oracle client connects to the internal load balancer frontend IP address 10.0.1.100 (Port 1521) to connect to the Oracle listener.
- The primary node (lk-node01 / 10.0.101.11) and the secondary node (lk-node02 / 10.0.101.12) are registered as the internal load balancer target (backend). The internal load balancer performs a health check for each node and checks which node has an unused port. The packet that is received for the Oracle listener is transferred to the node. Note: The port used to respond to the health check can be specified by using the LB Health Check. Only the node where the LB Health Check is provided can respond to the health check.
Post your comment on this topic.