[Client Side Caching] not sharing cache with connections? #62
YangWoomin
started this conversation in
General
Replies: 1 comment
-
|
Hi @YangWoomin, the invalidation of key A was sent after your second goroutine updated the key. So yes, your first goroutine could get the old value before processing the invalidation, but the gap should be small. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a problem for optimistic lock update test.
When one go routine gets value with key A just after the other sets value with key A, the first go routine gets old value.
Is it right that the connections aren't sharing client cache?
Beta Was this translation helpful? Give feedback.
All reactions