Redis主从持久化测试-mysql教程-PHP中文網

首頁

資料庫

mysql教程

Redis主从持久化测试

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 05:41 PM

redis耐力

1:redis主从环境，均未开启持久化；当主实例宕机，从实例上的数据不受影响；当主恢复后，主实例上的数据将会继续同步到从实例，即原来的值将变为空值；[root@ser

1:redis主从环境，均未开启持久化；
当主实例宕机，从实例上的数据不受影响；
当主恢复后，主实例上的数据将会继续同步到从实例，即原来的值将变为空值；

[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.112 -a 123 info |grep -A 3 'Replication'
# Replication
role:master
connected_slaves:1
slave0:192.168.1.113,6379,online

[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.112 -a 123
redis 192.168.1.112:6379> set 1 a
OK
redis 192.168.1.112:6379> get 1
"a"

[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.112 -a 123 shutdown

[root@server12 ~]# tail -f /var/log/messages
Dec 3 15:27:34 server12 redis[32151]: Connecting to MASTER...
Dec 3 15:27:34 server12 redis[32151]: MASTER SLAVE sync started
Dec 3 15:27:34 server12 redis[32151]: Error condition on socket for SYNC: Connection refused

[root@server12 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.113 -a 123
redis 192.168.1.113:6379> get 1
"a"

[root@server11 ~]# /usr/local/redis2/bin/redis-server /usr/local/redis2/etc/redis.conf
[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.112 -a 123
redis 192.168.1.112:6379> get 1
(nil)
redis 192.168.1.112:6379> exit

[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.113 -a 123
redis 192.168.1.113:6379> get 1
(nil)

2：redis主从环境，香港服务器，从实例开启快照持久化
当主实例宕机，从实例上的数据不受影响；
当主恢复后，主实例上的数据将会继续同步到从实例，即原来的值将变为空值；

[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.112 -a 123
redis 192.168.1.112:6379> get 1
(nil)
redis 192.168.1.112:6379> set 1 a
OK
redis 192.168.1.112:6379> set 2 b
OK
redis 192.168.1.112:6379> exit

[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.112 -a 123 shutdown

[root@server12 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.113 -a 123
redis 192.168.1.113:6379> get 1
"a"
redis 192.168.1.113:6379> get 2
"b"
redis 192.168.1.113:6379> exit

[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.112 -a 123
redis 192.168.1.112:6379> get 1
(nil)
redis 192.168.1.112:6379> get 2
(nil)
redis 192.168.1.112:6379> exit

[root@server12 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.113 -a 123
redis 192.168.1.113:6379> get 1
(nil)
redis 192.168.1.113:6379> get 2
(nil)
redis 192.168.1.113:6379> exit

3：推进一层，当主，从实例均宕机的情况下会如何呢？

[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.112 -a 123
redis 192.168.1.112:6379> set 1 a
OK
redis 192.168.1.112:6379> set 2 b
OK
redis 192.168.1.112:6379> set 3 c
OK
redis 192.168.1.112:6379> exit
[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.113 -a 123
redis 192.168.1.113:6379> get 1
"a"
redis 192.168.1.113:6379> get 2
"b"
redis 192.168.1.113:6379> get 3
"c"
redis 192.168.1.113:6379> exit

这次先关闭从实例，香港服务器租用，再关闭主实例！启动则先启动从实例，测试数据；再启动主实例，美国空间，再测试数据！
[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.112 -a 123 shutdown
[root@server12 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.113 -a 123 shutdown
[root@server12 ~]# /usr/local/redis2/bin/redis-server /usr/local/redis2/etc/redis.conf

[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.113 -a 123
redis 192.168.1.113:6379> get 1
"a"
redis 192.168.1.113:6379> get 2
"b"
redis 192.168.1.113:6379> get 3
"c"

[root@server11 ~]# /usr/local/redis2/bin/redis-server /usr/local/redis2/etc/redis.conf
[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.112 -a 123
redis 192.168.1.112:6379> get 1
(nil)
redis 192.168.1.112:6379> get 2
(nil)
redis 192.168.1.112:6379> get 3
(nil)
redis 192.168.1.112:6379> exit

[root@server11 ~]# /usr/local/redis2/bin/redis-cli -h 192.168.1.113 -a 123
redis 192.168.1.113:6379> get 1
(nil)
redis 192.168.1.113:6379> get 2
(nil)
redis 192.168.1.113:6379> get 3
(nil)
redis 192.168.1.113:6379> exit

实践证明，在redis主从读写分离条件下，快照持久化只有开在主实例侧才可以保证数据可以跨越实例重启！

陳述

本文內容由網友自願投稿，版權歸原作者所有。本站不承擔相應的法律責任。如發現涉嫌抄襲或侵權的內容，請聯絡admin@php.cn

如何在MySQL中刪除或修改現有視圖？May 16, 2025 am 12:11 AM

todropaviewInmySQL，使用“ dropviewifexistsview_name;” andTomodifyAview，使用“ createOrreplaceViewViewViewview_nameAsSelect ...”。 whendroppingaview，asew dectivectenciesanduse和showcreateateviewViewview_name;“ tounderStanditSsstructure.whenModifying

MySQL視圖：我可以使用哪些設計模式？May 16, 2025 am 12:10 AM

mySqlViewScaneFectectialized unizedesignpatternslikeadapter，Decorator，Factory，andObserver.1）adapterPatternadaptSdataForomDifferentTablesIntoAunifiendView.2）decoratorPatternenhancateDataWithCalcalcualdCalcalculenfields.3）fieldfields.3）

在MySQL中使用視圖的優點是什麼？May 16, 2025 am 12:09 AM

查看InMysqlareBeneForsImplifyingComplexqueries，增強安全性，確保dataConsistency，andOptimizingPerformance.1）他們simimplifycomplexqueriesbleiesbyEncapsbyEnculatingThemintoreusableviews.2）viewsEnenenhancesecuritybyControllityByControllingDataAcces.3）

如何在MySQL中創建一個簡單的視圖？May 16, 2025 am 12:08 AM

toCreateAsimpleViewInmySQL，USEthecReateaTeviewStatement.1）defitEtheetEtheTeViewWithCreatEaTeviewView_nameas.2）指定usethectstatementTorivedesireddata.3）usethectStatementTorivedesireddata.3）usetheviewlikeatlikeatlikeatlikeatlikeatlikeatable.views.viewssimplplifefifydataaccessandenenanceberity but consisterfort，butconserfort，consoncontorfinft

MySQL創建用戶語句：示例和常見錯誤May 16, 2025 am 12:04 AM

1）foralocaluser：createUser'localuser'@'@'localhost'Indidendify'securepassword'; 2）foraremoteuser：creationuser's creationuser'Remoteer'Remoteer'Remoteer'Remoteer'Remoteer'Remoteer'Remoteer'Remoteer'Rocaluser'@'localhost'Indidendify'seceledify'Securepassword'; 2）

在MySQL中使用視圖的局限性是什麼？May 14, 2025 am 12:10 AM

mysqlviewshavelimitations：1）他們不使用Supportallsqloperations，限制DatamanipulationThroughViewSwithJoinsOrsubqueries.2）他們canimpactperformance，尤其是withcomplexcomplexclexeriesorlargedatasets.3）

確保您的MySQL數據庫：添加用戶並授予特權May 14, 2025 am 12:09 AM

porthusermanagementinmysqliscialforenhancingsEcurityAndsingsmenting效率databaseoperation.1）usecReateusertoAddusers，指定connectionsourcewith@'localhost'or@'％'。

哪些因素會影響我可以在MySQL中使用的觸發器數量？May 14, 2025 am 12:08 AM

mysqldoes notimposeahardlimitontriggers，butacticalfactorsdeterminetheireffactective：1）serverConfiguration impactactStriggerGermanagement; 2）複雜的TriggerSincreaseSySystemsystem load; 3）largertablesslowtriggerperfermance; 4）highConconcConcrencerCancancancancanceTigrignecentign; 5）; 5）

See all articles