Skip to content

replication: removing anonymous replicas from synchro quorum #2600

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

Closed
Tracked by #2601
art-dr opened this issue Jan 21, 2022 · 0 comments · Fixed by #3105
Closed
Tracked by #2601

replication: removing anonymous replicas from synchro quorum #2600

art-dr opened this issue Jan 21, 2022 · 0 comments · Fixed by #3105
Labels
server [area] Task relates to Tarantool's server (core) functionality

Comments

@art-dr
Copy link
Contributor

art-dr commented Jan 21, 2022

Since: 2.10.0-beta2
Root document: https://www.tarantool.io/en/doc/latest/book/replication/repl_sync/#usage
SME: @ kyukhin
dev issue: tarantool/tarantool#5418

Details

In tarantool/tarantool@04b2230 it is said that "Transactions should be committed after they reach quorum of "real" cluster members. Therefore, anonymous replicas shouldn't participate in the quorum"

Documentation says: "This option tells how many replicas should confirm the receipt of a synchronous transaction before it is committed. So far, this option accounts for all replicas including anonymous ones."

Correct the text so it says that anonymous replicas don't participate in the quorum since 2.10.0.

@art-dr art-dr added the server [area] Task relates to Tarantool's server (core) functionality label Jan 21, 2022
@art-dr art-dr added the 1sp label Jan 26, 2022
@art-dr art-dr changed the title [1pt] replication: removing anonymous replicas from synchro quorum replication: removing anonymous replicas from synchro quorum Jan 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
server [area] Task relates to Tarantool's server (core) functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant