Skip to content
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

Introduce replication_sync_timeout configuration option #3647

Closed
locker opened this issue Aug 27, 2018 · 1 comment
Closed

Introduce replication_sync_timeout configuration option #3647

locker opened this issue Aug 27, 2018 · 1 comment
Assignees
Labels
feature A new functionality replication
Milestone

Comments

@locker
Copy link
Member

locker commented Aug 27, 2018

box.cfg{replication = ...} doesn't return until it synchronizes with a quorum, i.e. until the replication lag is less than box.cfg.replication_sync_lag for at least box.cfg.replication_connect_quorum replicas (currently, it's true only in case of initial configuration; replication reconfiguration case will be fixed in the scope of #3427). If replication_sync_lag happens to be smaller than the network latency, box.cfg() will never return, neither can it be cancelled. We should probably introduce a new option box.cfg.replication_sync_timeout and make box.cfg() raise an error or leave the server in the 'orphan' state if it failed to sync within the specified timeout.

@locker locker added feature A new functionality replication labels Aug 27, 2018
@OKriw OKriw self-assigned this Aug 27, 2018
@kyukhin kyukhin added this to the 1.9.2 milestone Aug 30, 2018
@locker
Copy link
Member Author

locker commented Sep 4, 2018

Fixed by ca9fc33

@locker locker closed this as completed Sep 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new functionality replication
Projects
None yet
Development

No branches or pull requests

3 participants