公司的实战 Replica Sets+Sharding 方案 公司 mongo 集群分片实战 准备九台服务器, 分片 1 : 172.16.0.124:11731 主 172.16.0.127.11731 备 172.16.0.115:11731 仲裁 分片 2 : 172.16.0.122:11732 主 172.16.0.125:11732 备 172.16.0.103:11732 仲裁 分片
公司的实战Replica Sets+Sharding方案
公司mongo集群分片实战
准备九台服务器,
分片1:
172.16.0.124:11731 主
172.16.0.127.11731 备
172.16.0.115:11731 仲裁
分片2:
172.16.0.122:11732 主
172.16.0.125:11732 备
172.16.0.103:11732 仲裁
分片3:
172.16.0.121:11733 主
172.16.0.123:11733 备
172.16.0.114:11733 仲裁
分片1步骤
--172.16.0.124分片1主
创建目录
mkdir -p /home/data/shard1_1
mkdir -p /home/Apps
tar zxvf mongodb-linux-x86_64-2.4.7.tgz
mv mongodb-linux-x86_64-2.4.7 /home/Apps/mongo
启动服务
/home/Apps/mongo/bin/mongod --shardsvr --replSet shard1 --port 11731 --dbpath /home/data/shard1_1 --logpath /home/data/shard1_1/shard1_1.log --logappend --oplogSize 5000 --fork
--172.16.0.127分片1备
mkdir -p /home/data/shard1_2
mkdir -p /home/Apps
tar zxvf mongodb-linux-x86_64-2.4.7.tgz
mv mongodb-linux-x86_64-2.4.7 /home/Apps/mongo
启动服务
/home/Apps/mongo/bin/mongod --shardsvr --replSet shard1 --port 11731 --dbpath /home/data/shard1_2 --logpath /home/data/shard1_2/shard1_2.log --logappend --oplogSize 5000 --fork
--172.16.0.115分片1仲载
mkdir -p /home/data/shard1_3
mkdir -p /home/Apps
mkdir -p /home/data/config
tar zxvf mongodb-linux-x86_64-2.4.7.tgz
mv mongodb-linux-x86_64-2.4.7 /home/Apps/mongo
/home/Apps/mongo/bin/mongod --shardsvr --replSet shard1 --port 11731 --dbpath /home/data/shard1_3 --logpath /home/data/shard1_3/shard1_3.log --logappend --oplogSize 5000 --fork
分片1启动好,初始化Replica Set1 arbiterOnly:true仲裁
在分片1主 172.16.0.124操作如下
/home/Apps/mongo/bin/mongo --port 11731
config={_id:'shard1',members:[{_id:0,host:'172.16.0.124:11731'},{_id:1,host:'172.16.0.127:11731'},{_id:2,host:'172.16.0.115:11731',arbiterOnly:true}]}
rs.initiate(config)
------------------------------------------------------------------------------------------------------------------------------
分片2步骤
--172.16.0.122分片2主
创建目录
mkdir -p /home/data/shard2_1
mkdir -p /home/Apps
tar zxvf mongodb-linux-x86_64-2.4.7.tgz
mv mongodb-linux-x86_64-2.4.7 /home/Apps/mongo
启动服务
/home/Apps/mongo/bin/mongod --shardsvr --replSet shard2 --port 11732 --dbpath /home/data/shard2_1 --logpath /home/data/shard2_1/shard2_1.log --oplogSize 50000 --logappend --fork
--172.16.0.125分片2备
mkdir -p /home/data/shard2_2
mkdir -p /home/Apps
tar zxvf mongodb-linux-x86_64-2.4.7.tgz
mv mongodb-linux-x86_64-2.4.7 /home/Apps/mongo
启动服务
/home/Apps/mongo/bin/mongod --shardsvr --replSet shard2 --port 11732 --dbpath /home/data/shard2_2 --logpath /home/data/shard2_2/shard2_2.log --oplogSize 50000 --logappend --fork
--172.16.0.103分片2仲载
mkdir -p /home/data/shard2_3
mkdir -p /home/Apps
mkdir -p /home/data/config
tar zxvf mongodb-linux-x86_64-2.4.7.tgz
mv mongodb-linux-x86_64-2.4.7 /home/Apps/mongo
/home/Apps/mongo/bin/mongod --shardsvr --replSet shard2 --port 11732 --dbpath /home/data/shard2_3 --logpath /home/data/shard2_3/shard2_3.log --oplogSize 50000 --logappend --fork
分片2启动好,初始化Replica Set 2 arbiterOnly:true仲裁
在分片2主 172.16.0.122操作如下
/home/Apps/mongo/bin/mongo --port 11732
config={_id:'shard2',members:[{_id:0,host:'172.16.0.122:11732'},{_id:1,host:'172.16.0.125:11732'},{_id:2,host:'172.16.0.103:11732',arbiterOnly:true}]}
rs.initiate(config)
-----------------------------------------------------------------------------------------------------------
分片3步骤
--172.16.0.121分片3主
创建目录
mkdir -p /home/data/shard3_1
mkdir -p /home/Apps
tar zxvf mongodb-linux-x86_64-2.4.7.tgz
mv mongodb-linux-x86_64-2.4.7 /home/Apps/mongo
启动服务
/home/Apps/mongo/bin/mongod --shardsvr --replSet shard3 --port 11733 --dbpath /home/data/shard3_1 --logpath /home/data/shard3_1/shard3_1.log --oplogSize 50000 --logappend --fork
--172.16.0.123分片3备
mkdir -p /home/data/shard2_2
mkdir -p /home/Apps
tar zxvf mongodb-linux-x86_64-2.4.7.tgz
mv mongodb-linux-x86_64-2.4.7 /home/Apps/mongo
启动服务
/home/Apps/mongo/bin/mongod --shardsvr --replSet shard3 --port 11733 --dbpath /home/data/shard3_2 --logpath /home/data/shard3_2/shard3_2.log --oplogSize 50000 --logappend --fork
--172.16.0.114分片3仲载
mkdir -p /home/data/shard3_3
mkdir -p /home/Apps
mkdir -p /home/data/config
tar zxvf mongodb-linux-x86_64-2.4.7.tgz
mv mongodb-linux-x86_64-2.4.7 /home/Apps/mongo
/home/Apps/mongo/bin/mongod --shardsvr --replSet shard3 --port 11733 --dbpath /home/data/shard3_3 --logpath /home/data/shard3_3/shard3_3.log --oplogSize 50000 --logappend --fork
分片3启动好,初始化Replica Set 3 arbiterOnly:true仲裁
在分片3主 172.16.0.121操作如下
/home/Apps/mongo/bin/mongo --port 11733
config={_id:'shard3',members:[{_id:0,host:'172.16.0.121:11733'},{_id:1,host:'172.16.0.123:11733'},{_id:2,host:'172.16.0.114:11733',arbiterOnly:true}]}
rs.initiate(config)
配置3个分片Config Server
在172.16.0.115,172.16.0.103,172.16.0.114 这三台执行操作,如下面代码
/home/Apps/mongo/bin/mongod --configsvr --dbpath /home/data/config --port 30000 --logpath /home/data/config/config.log --logappend --fork
配置3个分片Route Process
在172.16.0.115,172.16.0.103,172.16.0.114 这三台执行操作,如下面代码
/home/Apps/mongo/bin/mongos --configdb 172.16.0.115:30000,172.16.0.103:30000,172.16.0.114:30000 -port 60000 --chunkSize 1 --logpath /home/data/mongos.log --logappend --fork
配置Shard Cluster
在172.16.0.115,172.16.0.103,172.16.0.114 这三台其中一台执行操作,如下面代码
/home/Apps/mongo/bin/mongo --port 60000
use admin
db.runCommand({addshard:"shard1/172.16.0.124:11731, 172.16.0.127:11731, 172.16.0.115:11731"})
db.runCommand({addshard:"shard2/172.16.0.122:11732, 172.16.0.125:11732, 172.16.0.103:11732"})
db.runCommand({addshard:"shard3/172.16.0.121:11733, 172.16.0.123:11733, 172.16.0.114:11733"})
接下来激活分片,如下面的代码所示: 采用hash分片
db.runCommand({enablesharding:"test"})
db.runCommand({shardcollection:"test.users",key:{id:"hashed"}})
强调服务时间必须要同步,否则有问题

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

Atom editor mac version download
The most popular open source editor

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

Zend Studio 13.0.1
Powerful PHP integrated development environment

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software