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
However, I keep reading stale data from lua binding after nodejs complete the write operation. Therefore, I would like to specify read and write concern on both side to ensure no stale data.
As far as I know, this binding doesn't implements write/read concerns... if you have more than one mongod instance, you can change your JS write increasing the argument of w:1, it would be better to use the same number as mongod instances you need to acknowledge. Currently I don't figure any other way to ensure write/read concerns using this binding. I will let this issue open for future implementation of read/write concerns.
I am running a single mongodb.
However, I keep reading stale data from lua binding after nodejs complete the write operation. Therefore, I would like to specify read and write concern on both side to ensure no stale data.
in nodejs, I ensure the write concern by
j
andw
.I have tried to wait for 10 seconds. It still reads the stale record.
But, I am not sure how to specify readConcern in this lua binding.
Or, are there any hints for not reading stale data?
The text was updated successfully, but these errors were encountered: