v3.5.3 版本不支持 sharding 模式

[liwanggui]

Describe the problem that you experienced

最新的 v3.5.3 版本不支持配置为 sharding 模式，v3.5.3 版本如何部署集群？

Enter the URL of the topic with the problem

https://github.com/OpenAtomFoundation/pika/wiki/Pika-Sharding-Tutorials

Describe what you were looking for in the documentation

No response

Describe the actions that led you to experience the problem

No response

Describe what you want to experience that would fix the problem

No response

Add a screenshot if that helps illustrate the problem

If this problem caused an exception or error, please paste it here

No response

If the problem is browser-specific, please specify the device, OS, browser, and version

No response

Provide any additional information here in as much as detail as you can

No response

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: v3.5.3 version does not support sharding mode

[AlexStocks]

U can deploy a v3.5.3 cluster by our https://github.com/OpenAtomFoundation/pika/tree/unstable/codis which is customized by our community.

[liwanggui]

您可以通过我们的社区定制的https://github.com/OpenAtomFoundation/pika/tree/unstable/codis部署 v3.5.3 集群 。

如何配置 pika sentinel 实现高可用？？

想通过 redis-sentinel 实现主从自动切换，但在实验中 redis-sentinel 并不能将从库提升为主库。

实验环境:

• 192.168.110.110:9221 主
• 192.168.110.110:9222 从
• 192.168.110.110:9223 从

启动全部实例，主从连接正常。启动 redis-sentinel
手动将 192.168.110.110:9221 停止后，redis-sentinel 日志输出如下:

529442:X 08 Apr 2024 16:08:24.235 # +sdown master mymaster 192.168.110.110 9221
529442:X 08 Apr 2024 16:08:24.235 # +odown master mymaster 192.168.110.110 9221 #quorum 1/1
529442:X 08 Apr 2024 16:08:24.235 # +new-epoch 1
529442:X 08 Apr 2024 16:08:24.235 # +try-failover master mymaster 192.168.110.110 9221
529442:X 08 Apr 2024 16:08:24.250 # +vote-for-leader 48db312ada09ed50cc9568fab607127ad4c7f66c 1
529442:X 08 Apr 2024 16:08:24.250 # +elected-leader master mymaster 192.168.110.110 9221
529442:X 08 Apr 2024 16:08:24.250 # +failover-state-select-slave master mymaster 192.168.110.110 9221
529442:X 08 Apr 2024 16:08:24.310 # +selected-slave slave 192.168.110.110:9223 192.168.110.110 9223 @ mymaster 192.168.110.110 9221
529442:X 08 Apr 2024 16:08:24.310 * +failover-state-send-slaveof-noone slave 192.168.110.110:9223 192.168.110.110 9223 @ mymaster 192.168.110.110 9221
529442:X 08 Apr 2024 16:08:24.365 * +failover-state-wait-promotion slave 192.168.110.110:9223 192.168.110.110 9223 @ mymaster 192.168.110.110 9221
529442:X 08 Apr 2024 16:08:55.034 # +sdown slave 192.168.110.110:9223 192.168.110.110 9223 @ mymaster 192.168.110.110 9221

查看2个从节点信息，除了 master_link_status 变成 down 以外没有任何变化。

[root@localhost etc]# redis-cli -p 9222 info Replication
# Replication(SLAVE)
role:slave
ReplicationID:2decb9d62e6c2767375b1aaa1add389ae721d46dbc78bc29ac
master_host:192.168.110.110
master_port:9221
master_link_status:down
slave_priority:90
slave_read_only:1
db_repl_state:(db0:NoConnect)(db1:NoConnect)(db2:NoConnect)(db3:NoConnect)(db4:NoConnect)(db5:NoConnect)(db6:NoConnect)(db7:NoConnect)
db0:binlog_offset=0 0,safety_purge=none
db1:binlog_offset=0 0,safety_purge=none
db2:binlog_offset=0 0,safety_purge=none
db3:binlog_offset=0 0,safety_purge=none
db4:binlog_offset=0 0,safety_purge=none
db5:binlog_offset=0 0,safety_purge=none
db6:binlog_offset=0 0,safety_purge=none
db7:binlog_offset=0 0,safety_purge=none

[root@localhost etc]# redis-cli -p 9223 info Replication
# Replication(SLAVE)
role:slave
ReplicationID:2decb9d62e6c2767375b1aaa1add389ae721d46dbc78bc29ac
master_host:192.168.110.110
master_port:9221
master_link_status:down
slave_priority:80
slave_read_only:1
db_repl_state:(db0:NoConnect)(db1:NoConnect)(db2:NoConnect)(db3:NoConnect)(db4:NoConnect)(db5:NoConnect)(db6:NoConnect)(db7:NoConnect)
db0:binlog_offset=0 0,safety_purge=none
db1:binlog_offset=0 0,safety_purge=none
db2:binlog_offset=0 0,safety_purge=none
db3:binlog_offset=0 0,safety_purge=none
db4:binlog_offset=0 0,safety_purge=none
db5:binlog_offset=0 0,safety_purge=none
db6:binlog_offset=0 0,safety_purge=none
db7:binlog_offset=0 0,safety_purge=none

[AlexStocks]

我们借鉴 sentinel，把它的功能已经做到了 codis dashboard 里面了，也即我们定制的 codis 原生支持 master-slave auto-failover。

目前 pika 对原生 sentinel 的支持还有些问题，需要改进。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

We learned from sentinel and integrated its functions into the codis dashboard, that is, our customized codis natively supports master-slave auto-failover.

Currently, pika's support for native sentinel still has some problems and needs to be improved.

[937988621]

我们借鉴 sentinel，把它的功能已经做到了 codis dashboard 里面了，也即我们定制的 codis 原生支持 master-slave auto-failover。

目前 pika 对原生 sentinel 的支持还有些问题，需要改进。

你好，请问 codis 配合pika能实现1master2slave的故障转移吗？我这边有一个业务并不需要用cluster模式，只需要普通的主从pika能实现故障转移即可，类似redis哨兵模式

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

We learn from sentinel and integrate its functions into the codis dashboard, that is, our customized codis natively supports master-slave auto-failover.

Currently, pika’s support for native sentinel still has some problems and needs to be improved.

Hello, can codis cooperate with pika to achieve failover of 1master2slave? I have a business here that does not need to use cluster mode. It only needs ordinary master-slave Pika to achieve failover, similar to redis sentinel mode.