When node has not initialized in raft mode
Is this a regression?
Yes
Description
在 raft 模式下,应当首先初始化节点再进行读写操作。在开发时使用 assert 保证读写命令执行时,node 一定被初始化了。
现在需要增加对此的错误处理,在raft模式下,如果在节点初始化之前进行读写,应当向 client 返回错误信息,而不是触发 assert 崩溃。
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response
Pika支持哨兵
好的,谢谢,有微信交流群吗?
我们用QQ交流群: 294254078
我在使用的时候碰到这样一个问题:日志中报了Max connection reach
W0706 13:49:38.323585 10684 pika_dispatch_thread.cc:65] Max connections reach, Deny new comming: 192.168.1.219 W0706 13:49:38.323662 10684 pika_dispatch_thread.cc:65] Max connections reach, Deny new comming: 192.168.1.219 W0706 13:49:38.323755 10684 pika_dispatch_thread.cc:65] Max connections reach, Deny new comming: 192.168.1.219 W0706 13:49:38.323896 10684 pika_dispatch_thread.cc:65] Max connections reach, Deny new comming: 192.168.1.219 W0706 13:49:38.324008 10684 pika_dispatch_thread.cc:65] Max connections reach, Deny new comming: 192.168.1.219 W0706 13:49:38.324189 10684 pika_dispatch_thread.cc:65] Max connections reach, Deny new comming: 192.168.1.219 W0706 13:49:38.324286 10684 pika_dispatch_thread.cc:65] Max connections reach, Deny new comming: 192.168.1.219 W0706 13:49:38.324365 10684 pika_dispatch_thread.cc:65] Max connections reach, Deny new comming: 192.168.1.219 W0706 13:49:38.324461 10684 pika_dispatch_thread.cc:65] Max connections reach, Deny new comming: 192.168.1.219 [root@localhost log]#
我们服务器的配置: [root@localhost conf]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 61261 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 102400 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 102400 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
Pika的配置是: dump-expire : 0
pidfile Path
pidfile : ./pika.pid
Max Connection
maxclients : 20000
目前服务器上没其它的服务,重启Pika后一切正常。
请问之前碰到过类似问题吗?有什么线索吗?
这个应该是你pika上连接的客户端已经达到上限了, 你可以执行info clients看一下pika当前的连接量是多少, 这个上限可以在配置文件中进行修改
我回来再看看吧,之前看client应该是6000多,我设置的maxclients : 20000,所以有点奇怪。