You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Question about the correct usage of "wait". According to the redis docs "wait" command "returns when all the previous write commands sent in the context of the current connection are guaranteed to be received by the number of replicas". Since the library uses connection pooling how one can make sure that "wait" returns the number of replicas from a specific command and not something else that was running concurrently?
In my understanding, both commands in the following code just pick available connections from the pool without any
'stickiness' which might yield incorrect resulsts.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Question about the correct usage of "wait". According to the redis docs "wait" command "returns when all the previous write commands sent in the context of the current connection are guaranteed to be received by the number of replicas". Since the library uses connection pooling how one can make sure that "wait" returns the number of replicas from a specific command and not something else that was running concurrently?
In my understanding, both commands in the following code just pick available connections from the pool without any
'stickiness' which might yield incorrect resulsts.
Beta Was this translation helpful? Give feedback.
All reactions