predixy icon indicating copy to clipboard operation
predixy copied to clipboard

A high performance and fully featured proxy for redis, support redis sentinel and redis cluster

Results 112 predixy issues
Sort by recently updated
recently updated
newest added

``` /predixy # cat /etc/os-release NAME="Alpine Linux" ID=alpine VERSION_ID=3.8.0 PRETTY_NAME="Alpine Linux v3.8" HOME_URL="http://alpinelinux.org" BUG_REPORT_URL="http://bugs.alpinelinux.org" /predixy # make make[1]: Entering directory '/predixy/src' g++ -std=c++11 -Wall -w -g -O3 -D_PREDIXY_BACKTRACE_ -D_EPOLL_ -c...

由于 [https://github.com/openresty/lua-resty-redis ](url) openresty/lua-resty-redis,不支持cluster模式,所以我用predixy代理。当我在压测nginx性能时,predixy出现大量CLOSE_WAITE请求未关闭情况。导致nginx连接不上predixy。有可能是我哪里配置不对嘛,或者predixy有bug。 predixy :1.0.5 release cluster config: ``` ClusterServerPool { MasterReadPriority 60 StaticSlaveReadPriority 50 DynamicSlaveReadPriority 50 RefreshInterval 1 ServerFailureLimit 10 ServerRetryTimeout 1 Password "xxx" Servers { + xxx:xxx...

背景: 我们在容器云内部署redis集群,redis版本为5.0,打包predixy最新release-1.0.5作为代理,redis+predixy整套环境部署于容器云内。 部署情况: redis-operator调度redis各实例,redis集群为3*3的cluster。predixy作为deployment部署,replica=2,通过LB对外提供服务。 predixy配置: ``` ClusterServerPool { Password xxxxxxxxx MasterReadPriority 60 StaticSlaveReadPriority 50 DynamicSlaveReadPriority 50 RefreshInterval 1 ServerTimeout 30 ServerFailureLimit 10 ServerRetryTimeout 1 KeepAlive 120 Servers { + redis-slave-2.redis-slave.redis-community:6379...

架构背景: 一个predixy代理,底下是6个redis实例,没有从节点也没有用哨兵。 使用场景: 用来作为日志的代理中间件的。日志通过predixy代理写到redis实例中。 结论: predixy跑一段时间后(具体时间不确定),使用到现在出现过2次情况 1.进程是存在的,但是报错连不上predixy,由于当时忙着恢复,没有去telnet去测试。重启后恢复 2.predixy服务正常,但是会出现部分丢数据的现象,期间predixy的日志没有什么明显的报错,重启也是立马恢复。

Its performance is excellent. But it's not updated a long time. Is it still maitained? Are there many people using this? Thanks.

Hi, While connecting to cluster mode redis server through predixy proxy using java redis cluster client trying to **execute cluster nodes/cluster info commands** to verify is redis in standalone or...

predixy version: predixy-1.0.5-pre 操作系统版本:CentOS Linux release 7.4.1708 (Core) ``` 2020-12-01 11:36:52.793291 E Backtrace.h:18 predixy backtrace(11) /usr/bin/predixy(_Z9traceInfoi+0x12f)[0x4b3d3f] /usr/bin/predixy[0x4b2b1d] /lib64/libc.so.6(+0x35270)[0x7f5a79dc6270] /usr/bin/predixy(_ZNK7Request6isDoneEv+0x0)[0x486c00] /usr/bin/predixy(_ZN16AcceptConnection4sendEP7HandlerP7RequestP8Response+0x22)[0x450e72] /usr/bin/predixy(_ZN7Handler14handleResponseEP17ConnectConnectionP7RequestP8Response+0x25c)[0x4a9c6c] /usr/bin/predixy(_ZN7Handler14directResponseEP7RequestN8Response11GenericCodeEP17ConnectConnection+0x12a)[0x4aa8ba] /usr/bin/predixy(_ZN17ConnectConnection5closeEP7Handler+0xa9)[0x45b2a9] /usr/bin/predixy(_ZN7Handler26postConnectConnectionEventEv+0x1ac)[0x4a60fc] /usr/bin/predixy(_ZN7Handler3runEv+0x108)[0x4a8bf8] /usr/bin/predixy(execute_native_thread_routine+0x20)[0x4f4b60] /lib64/libpthread.so.0(+0x7e25)[0x7f5a7a673e25] /lib64/libc.so.6(clone+0x6d)[0x7f5a79e8934d] 2020-12-01 11:36:52.794259...

你好,我现在有redis cluster部署在k8s上,statefulset部署,版本5.0.9-alpine,用predixy作为proxy。predixy一开始运行良好,但是过一段时间后日志内就会大量报错,甚至直接拒绝连接 ERR no server connection avaliable,需要重启pod才能把error消除。但是过一段时间后error又会重现。 查询了一下之前的[issue](https://github.com/joyieldInc/predixy/issues/53),发现其他人也有类似的问题,但似乎这个这个问题还没解决。请问这个问题如何解决? 以下是部分日志: 2020-09-28 18:19:43.269529 E Handler.cpp:437 h 1 s cnx-bionix-facial-monitor-redis-4.cnx-bionix-facial-monitor-redis-headless.cnx-bionix-facial-monitor.svc.cluster.local:6379 19 will be close with status 4 EventError 2020-09-28 18:19:43.269557 E Handler.cpp:437 h...