chendali16
chendali16
使用阿里云ecs 然后jedis 连接redis clusters 消费数据有40ms的延迟,看资料这个跟内核tcp设计有关?如何避免该情况
> Consumers who subscribe to the queue will push, and only push real-time data.This means that the redis consumes data by itself and push data to consumers in multiple threads....
> It feels like you are missing something, `XGROUPREAD`is mutually exclusive, if message A is consumed by consumer c1, c2 will not receive message A. If we use push, we...
> Normally, the network latency would be much less than the time consumer consume message, so why do you need such a low latency? Our services are deployed on the...
> @chendali16 Do you effectively want to have a way to subscribe, like pubsub subscribe, to a stream? I feel like this is a feature that has been asked for...
> Interesting, I've seen reverse request as well to persist PUBSUB data to stream. We need to build some form of interoperability between these two. > > > Consumers who...
> I was thinking more on this. > > @chendali16 Doesn't the `BLOCK` option in `XREAD`/`XREADGROUP` command solve this problem for you ? the `BLOCK` option still cannot solve the...
When we use xrange, we can only query the sequenceid of the stream key, but the sequenceid is required to be strictly incremented. Generally, the service ID cannot match. we...
Original query data is as follows: 127.0.0.1:6379> XREADGROUP GROUP mqGroup consumerB COUNT 2 STREAMS mq 1553585533795-2 1) 1) "mq" 2) 1) 1) "1553585533795-2" 2) 1) "msg" 2) "3" 3) "id"...
> @chendali16 please write in English Hello, Can this be supported? Alternatively, we can add a key and query the message data through the key?