zhixinwen commented on PR #3047: URL: https://github.com/apache/kvrocks/pull/3047#issuecomment-3049294284
> I'm not quite understand this statement. Redis also requires to wait for the number of replica's offset is fulfilled the watermark. And it should not be different with Redis in performance. > My understanding is in Redis each client knows its last write sequence number, so WAIT would only need to wait for its own write. In KVRocks, the following scenario is possible if I get the code correct: client1: SET K1 V1 (seq number: 1) client2: SET K2 V2 (seq number: 2) client1: WAIT 1 (it would be waiting for seq number 2, but in Redis it would wait for seq number 1) again I am not expert in either system, so I may be wrong here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
