一次和同事聊RAC中的负载均衡,聊到服务器端的分发机制时大家都说不清,再此总结一下以备后用。
一次和同事聊RAC中的负载均衡,聊到服务器端的分发机制时大家都说不清,再此总结一下以备后用。
负载均衡Load Balance
客户端load balance
服务器端load balance
客户端load balance
客户端发起应用请求时,首先通过tnsnames.ora中随机选择一个vip地址,,然后通过该vip地址发起请求。这个vip地址实际上就是连接高可用的核心。当客户端访问的实例宕机了,甚至vip已经漂移到其它存活节点,这次连接就失败了。通知服务(FAN)会立刻通知客户端采用其它的vip重新连接,客户端选择tnsnames.ora中的其它vip继续尝试,直到连接成功为止。如果不采用vip方式连接,而直接使用IP地址连接不行么?答案是行,但是连接失败后需要30秒才能通知到客户端,30秒的代价太大了,完全失去了高可用的意义。
客户端的load balance不会判断当前服务器的负载,它只是随机分发。包括11gR2推出的SCAN也不会判断服务器端负载,它按照注册的3个vip地址轮询分发。服务器端的负载是如何判断的呢,我们继续往下看。
服务器端load balance
服务器端的负载均衡是监听器remote listener和local listener来合作完成的。监听器将当前负载信息在LBA(Load Balance Advisor)中注册,并且可以根据服务时间和吞吐量来设定负载类型。如果是Web服务可以配置服务时间作为负载均衡的条件,如果是查询密集型操作可以配置吞吐量类型。
总结一下上面的描述,客户端通过vip来实现连接高可用,服务器端通过remote listener,local listener和LBA的配置实现load balance。
在load balance中有两个总要的概念:
FAN:Fast Application Notification
快速通知,主动推送机制。既通知集群之间的节点,也通知客户端端到集群。
LBA:Load Balance Advisor
负载均衡建议器
本文永久更新链接地址:

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

Key metrics for EXPLAIN commands include type, key, rows, and Extra. 1) The type reflects the access type of the query. The higher the value, the higher the efficiency, such as const is better than ALL. 2) The key displays the index used, and NULL indicates no index. 3) rows estimates the number of scanned rows, affecting query performance. 4) Extra provides additional information, such as Usingfilesort prompts that it needs to be optimized.

Usingtemporary indicates that the need to create temporary tables in MySQL queries, which are commonly found in ORDERBY using DISTINCT, GROUPBY, or non-indexed columns. You can avoid the occurrence of indexes and rewrite queries and improve query performance. Specifically, when Usingtemporary appears in EXPLAIN output, it means that MySQL needs to create temporary tables to handle queries. This usually occurs when: 1) deduplication or grouping when using DISTINCT or GROUPBY; 2) sort when ORDERBY contains non-index columns; 3) use complex subquery or join operations. Optimization methods include: 1) ORDERBY and GROUPB

MySQL/InnoDB supports four transaction isolation levels: ReadUncommitted, ReadCommitted, RepeatableRead and Serializable. 1.ReadUncommitted allows reading of uncommitted data, which may cause dirty reading. 2. ReadCommitted avoids dirty reading, but non-repeatable reading may occur. 3.RepeatableRead is the default level, avoiding dirty reading and non-repeatable reading, but phantom reading may occur. 4. Serializable avoids all concurrency problems but reduces concurrency. Choosing the appropriate isolation level requires balancing data consistency and performance requirements.

MySQL is suitable for web applications and content management systems and is popular for its open source, high performance and ease of use. 1) Compared with PostgreSQL, MySQL performs better in simple queries and high concurrent read operations. 2) Compared with Oracle, MySQL is more popular among small and medium-sized enterprises because of its open source and low cost. 3) Compared with Microsoft SQL Server, MySQL is more suitable for cross-platform applications. 4) Unlike MongoDB, MySQL is more suitable for structured data and transaction processing.

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

The MySQL learning path includes basic knowledge, core concepts, usage examples, and optimization techniques. 1) Understand basic concepts such as tables, rows, columns, and SQL queries. 2) Learn the definition, working principles and advantages of MySQL. 3) Master basic CRUD operations and advanced usage, such as indexes and stored procedures. 4) Familiar with common error debugging and performance optimization suggestions, such as rational use of indexes and optimization queries. Through these steps, you will have a full grasp of the use and optimization of MySQL.

MySQL's real-world applications include basic database design and complex query optimization. 1) Basic usage: used to store and manage user data, such as inserting, querying, updating and deleting user information. 2) Advanced usage: Handle complex business logic, such as order and inventory management of e-commerce platforms. 3) Performance optimization: Improve performance by rationally using indexes, partition tables and query caches.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

SublimeText3 Chinese version
Chinese version, very easy to use

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool

WebStorm Mac version
Useful JavaScript development tools

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment