-
Notifications
You must be signed in to change notification settings - Fork 0
Make Tarantool spaces synchronous again #51
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
Comments
ligurio
added a commit
that referenced
this issue
Nov 27, 2021
Accidentally option for enabling synchronous mode for spaces in bank tests was not used. It means that with Tarantool cluster we tested asynchronous replication that has lower consistency guarantess that synchronous (eventual consistency). This patch enables is_sync for all spaces used in bank tests. For other tests option "is_sync" was enabled in commit "Make spaces used in tests synchronous" (dfb4d45). Follows up #51
ligurio
added a commit
that referenced
this issue
Nov 30, 2021
Accidentally option for enabling synchronous mode for spaces in bank tests was not used. It means that with Tarantool cluster we tested asynchronous replication that has lower consistency guarantess that synchronous (eventual consistency). This patch enables is_sync for all spaces used in bank tests. For other tests option "is_sync" was enabled in commit "Make spaces used in tests synchronous" (dfb4d45). Follows up #51
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.
As described in documentation synchronous replication can be enabled per-space using the
is_sync
option. This option was missed after switching from Lua to SQL in tests.(was lost in 3214905)
It is not possible to change
is_sync
usingSET SESSION
in SQL:But it is possible to create Lua function in SQL and use
box.space.j:alter{is_sync = true}
in it.The text was updated successfully, but these errors were encountered: