Skip to content

feedback: Automated leader election | Tarantool #2924

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

Open
Tracked by #2802
TarantoolBot opened this issue Jun 6, 2022 · 4 comments
Open
Tracked by #2802

feedback: Automated leader election | Tarantool #2924

TarantoolBot opened this issue Jun 6, 2022 · 4 comments
Labels
behavior change [nature] Сhange in existing behavior factual error Factual error in functionality description replication [area] Related to Replication

Comments

@TarantoolBot
Copy link
Collaborator

<…>other internal things need direct
connection between the nodes.
|Also, if election is enabled on the node, it won’t replicate from any nodes except
the newest leader. This is done to avoid the issue when a new leader is elected,
but the old leader has somehow survived and tries to send more changes
to the other nodes.|

Term numbers also work as a kind of a filter.
For example, you <…>

https://www.tarantool.io/en/doc/latest/book/replication/repl_leader_elect/#leader-election-process

Это неправда. Можно просто удалить целиком этот кусок . Дополнительные пояснения не нужны, т к у нас всегда каждый из узлов принимает репликацию от всех.

@patiencedaur patiencedaur added factual error Factual error in functionality description behavior change [nature] Сhange in existing behavior labels Jun 7, 2022
@patiencedaur
Copy link
Contributor

Need to clarify the version since which the behavior changed.

@veod32 veod32 self-assigned this Jun 7, 2022
@sergepetrenko
Copy link
Contributor

This was fixed in commit tarantool/tarantool@b35e470
(first release - 2.10.0-beta1)
and backported to 2.7.3 and 2.8.2

@veod32
Copy link
Collaborator

veod32 commented Jun 9, 2022

Recently, devs have found a bug related to the point. Putting the doc issue on hold for a while.

@veod32
Copy link
Collaborator

veod32 commented Jun 16, 2022

Development to fix the issue is going on, and actual system behaviou can be seen on its completion. Moving the doc issue back to Backlog. To sync up with devs in mid-July.

@veod32 veod32 mentioned this issue Jun 16, 2022
19 tasks
@veod32 veod32 added the 2sp label Jun 20, 2022
@veod32 veod32 removed their assignment Mar 1, 2023
@veod32 veod32 added replication [area] Related to Replication and removed 2sp labels Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
behavior change [nature] Сhange in existing behavior factual error Factual error in functionality description replication [area] Related to Replication
Projects
None yet
Development

No branches or pull requests

4 participants