tendis failover use too much time

Open
#73 33 comments 0 reactions 2 assignees View on GitHub

@flywukong is already working on this.

Since Mar 8, 2021.

Assessment

This issue has not been assessed yet.

Description

enhancement

2 machine 192.168.149.15/192.168.149.27 centos7.7
3 instances in every machine
use latest release version: tendis-2.1.2-rocksdb-v5.13.4
192.168.149.15:51001 (master) -> 192.168.149.27:51001 (slave)
192.168.149.15:51002 (master) -> 192.168.149.27:51002 (slave)
192.168.149.15:51003 (master) -> 192.168.149.27:51003 (slave)
follow the instruction in http://tendis.cn/#/Tendisplus/%E8%BF%90%E7%BB%B4/new_cluster
redis-cli -c can set and get many keys successfully(moved related slots)
QQ截图20210225200845

but when I kill 192.168.149.15:51001, it can't failover and improved 192.168.149.27:51001 into master automatically, and I can't get any key, even which isn't in slots of down master.
doesn't tendis failover automatically?

QQ图片20210225200350
QQ图片20210225200536
QQ截图20210225200624

Dominant language
C++
Stars
3.2k
Forks
343
Avg merge
2h 13m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Tencent/Tendis

All issues in Tencent/Tendis

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.