zhixinwen commented on issue #3097:
URL: https://github.com/apache/kvrocks/issues/3097#issuecomment-3162303170

   Exactly as @git-hulk explains. To be clear, this bug can be very hard to 
trigger in reality. The script is a modified redis-benchmark 
(https://github.com/redis/redis/pull/14247) and it just sends SET + WAIT + SET 
+ WAIT... continuously.
   
   For a real client, even if it uses pipeline to call `SET A 1; WAIT; SET B 2; 
WAIT;`, more than likely it would be pushed once into KVRocks and be read into 
the `OnRead` callback at once. It is only an issue if the commands are ingested 
by separate `OnRead`  calls. It means either the commands are extremely large 
or the time gap between the commands are long. I have to write a raw TCP stream 
to reliability trigger the issue.
   


-- 
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]

Reply via email to