Open LinzWang opened 1 month ago
Bot detected the issue body's language is not English, translate it automatically.
Title: In the pika cluster built based on codis, when the pipeline imports data, the proxy reports an error and cannot be imported.
ubuntu中可以写入,但proxy日志有大量的错误,检查pika中数据正常写入。
错误信息和mac中的错误类似
2024/07/25 18:08:59 session.go:270: [ERROR] 2024-07-25 18:08:57 remote:127.0.0.1:58964, start_time(us):1721902137218354, duration(us): [90, 291263, 1695292], 1986646, tasksLen:8458, command:[HSET prop-user000000000049499 list00000000000000048true].
[stack]:
3 /pika/codis/pkg/proxy/session.go:270
pika/codis/v2/pkg/proxy.(*Session).loopWriter.func2
2 /pika/codis/pkg/proxy/request.go:156
pika/codis/v2/pkg/proxy.(*RequestChan).PopFrontAll
1 /pika/codis/pkg/proxy/session.go:226
pika/codis/v2/pkg/proxy.(*Session).loopWriter
0 /pika/codis/pkg/proxy/session.go:148
pika/codis/v2/pkg/proxy.(*Session).Start.func1.3
... ...
2024/07/25 18:08:59 session.go:270: [ERROR] 2024-07-25 18:08:57 remote:127.0.0.1:58964, start_time(us):1721902137218357, duration(us): [90, 291260, 1695330], 1986682, tasksLen:8459, command:[HSET prop-user000000000049499 list00000000000000049true].
[stack]:
3 /pika/codis/pkg/proxy/session.go:270
pika/codis/v2/pkg/proxy.(*Session).loopWriter.func2
2 /pika/codis/pkg/proxy/request.go:156
pika/codis/v2/pkg/proxy.(*RequestChan).PopFrontAll
1 /pika/codis/pkg/proxy/session.go:226
pika/codis/v2/pkg/proxy.(*Session).loopWriter
0 /pika/codis/pkg/proxy/session.go:148
pika/codis/v2/pkg/proxy.(*Session).Start.func1.3
Codis 不支持 pipline 命令,属于是正常现象
Bot detected the issue body's language is not English, translate it automatically.
Codis does not support the pipline command, which is normal.
Is this a regression?
Yes
Description
本地通过codis连接两个pika服务,目前测试时发现通过pipeline写入数据时,100个命令拼接的pipeline可以正常写入,1000个命令时proxy,初次可能成功,第二次一定会报错,且链接超时后才会退出。错误多次发生后会导致pika异常退出
codis-proxy错误信息如下:
pika 错误信息如下:
pika配置文件只修改了thead-num 为 2,proxy配置如下
python 测试脚本:
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
No response
Please provide the version you discovered this bug in (check about page for version information)
Anything else?
No response