Skip to content

GET.WATCH Notified Unexpectedly on GET Operation #1653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
irounik opened this issue Mar 25, 2025 · 3 comments
Open

GET.WATCH Notified Unexpectedly on GET Operation #1653

irounik opened this issue Mar 25, 2025 · 3 comments

Comments

@irounik
Copy link

irounik commented Mar 25, 2025

Steps to Reproduce

Open two terminals (T1 & T2)
T2:
GET.WATCH key1

T1:
SET key1 value1
GET key1

Expected output

T2 should get the "value1" for key "key1" only once.

T2:

localhost:7379> GET.WATCH key1
entered the watch mode for GET.WATCH key1
OK [fingerprint=765825083] value1

Observed output

T2 got "value1" twice. This is the first time for SET and the second for a GET command.

T2:

localhost:7379> GET.WATCH key1
entered the watch mode for GET.WATCH key1
OK [fingerprint=765825083] value1
OK [fingerprint=765825083] value1 // Got value for the second time when GET was called on T1
@irounik irounik changed the title GET.WATCH Notified Unexpectedly on GET Operation" GET.WATCH Notified Unexpectedly on GET Operation Mar 25, 2025
@SValanukonda
Copy link

SValanukonda commented Apr 13, 2025

hi @irounik and @arpitbbhayani what to add one more observation , even if set command fails , we are notifying watch clients

#Image

@SValanukonda
Copy link

hi @arpitbbhayani , fix is addressed in this PR #1688

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@irounik @SValanukonda and others