Skip to content

3.1版本的sentinel,在从众多的从中选举出新的主后,proxy退出 #1080

@ghost

Description

2016/12/14 13:07:05 router.go:218: [WARN] fill slot 0031, backend.addr = 192.168.34.6:6479, locked = false
2016/12/14 13:07:05 router.go:218: [WARN] fill slot 0032, backend.addr = 192.168.34.6:6479, locked = false
2016/12/14 13:07:05 router.go:218: [WARN] fill slot 0033, backend.addr = 192.168.34.6:6479, locked = false
2016/12/14 13:07:05 router.go:218: [WARN] fill slot 0034, backend.addr = 192.168.34.6:6479, locked = false
2016/12/14 13:07:05 router.go:218: [WARN] fill slot 0035, backend.addr = 192.168.34.6:6479, locked = false
2016/12/14 13:07:05 router.go:218: [WARN] fill slot 0036, backend.addr = 192.168.34.6:6479, locked = false
这个6479是sentinel选举出的新的主redis实例,但是proxy却无法连接,导致proxy异常退出,而且还是需要给新的主手动点击一下PROMPTE,然后proxy才好使

更重要的是 哨兵的日志里也都显示成功了,但是就是需要手动PROMPTE;而且手动提升主后,还需要点击哨兵的同步按钮,让哨兵知道现在主从的状态,所有一次完整的提升需要点击两次按钮,这样就根本没有解决ha的问题

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions