Open punisher1 opened 1 year ago
This may be because the "xreadgroup" command has been executed on the server before receiving the "timeout" result? It should never time out when reading is blocked.
Maybe you can refer to it https://github.com/StackExchange/StackExchange.Redis/issues/2135
2023-05-31T14:25:27.4733370+08:00 redis xreadgroup block read ... 2023-05-31T14:25:27.4976884+08:00 read message:1685514327495-0 2023-05-31T14:25:27.4994336+08:00 write message:1685514327495-0,1685514327498-0 2023-05-31T14:25:27.5082905+08:00 redis xreadgroup block read ... 2023-05-31T14:25:27.5101550+08:00 read message:1685514327498-0 2023-05-31T14:25:27.5107652+08:00 redis xreadgroup block read ... 2023-05-31T14:25:33.4848775+08:00 redis timeout ... 2023-05-31T14:25:33.4851831+08:00 redis xreadgroup block read ... 2023-05-31T14:25:37.5174767+08:00 write message:1685514337514-0,1685514337515-0 2023-05-31T14:25:37.5175269+08:00 read message:1685514337515-0 2023-05-31T14:25:37.5189520+08:00 redis xreadgroup block read ... 2023-05-31T14:25:43.4835083+08:00 redis timeout ... 2023-05-31T14:25:43.4837146+08:00 redis xreadgroup block read ... 2023-05-31T14:25:47.5262835+08:00 write message:1685514347525-0,1685514347526-0 2023-05-31T14:25:47.5262841+08:00 read message:1685514347526-0 2023-05-31T14:25:47.5276668+08:00 redis xreadgroup block read ... 2023-05-31T14:25:53.4743876+08:00 redis timeout ... 2023-05-31T14:25:53.4745574+08:00 redis xreadgroup block read ... 2023-05-31T14:25:57.5292349+08:00 write message:1685514357528-0,1685514357529-0 2023-05-31T14:25:57.5292381+08:00 read message:1685514357529-0 2023-05-31T14:25:57.5314306+08:00 redis xreadgroup block read ...