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.

Sign up for GitHub

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

Jump to bottom

Upon startup, a node that is leader should restore local log progress and re-apply log entries if it is single node cluster #883

Closed
Tracked by #881
drmingdrmer opened this issue Jun 29, 2023 · 1 comment · Fixed by #884
Closed
Tracked by #881

Upon startup, a node that is leader should restore local log progress and re-apply log entries if it is single node cluster #883

drmingdrmer opened this issue Jun 29, 2023 · 1 comment · Fixed by #884

Comments

@drmingdrmer
Copy link
Member

drmingdrmer commented Jun 29, 2023 •
edited
Loading

A node that is leader will continue being in leader state when restarted.
As a leader, the replication progress to itself can be restored.

And if this leader is the only node in a cluster, it should re-apply all of the logs to state machine at once.
@drmingdrmer drmingdrmer mentioned this issue Jun 29, 2023
Open
2 tasks
@github-actions
Copy link

👋 Thanks for opening this issue!

Get help or engage by:

  • /help : to print help messages.
  • /assignme : to assign this issue to you.

@drmingdrmer drmingdrmer changed the title A node that is leader should re-apply all log entries upon startup. Upon startup, a node that is leader should restore local log progress and re-apply log entries if it is single node cluster Jun 29, 2023
@drmingdrmer drmingdrmer mentioned this issue Jun 29, 2023
Merged
drmingdrmer added a commit to drmingdrmer/openraft that referenced this issue Jun 29, 2023
@drmingdrmer
Fix: restore replication progress when a leader starts up
f7a4ebd 
As a leader, the replication progress to itself should be restored upon
startup.

And if this leader is the only node in a cluster, it should re-apply all
of the logs to state machine at once.

- Fix: datafuselabs#883
drmingdrmer added a commit to drmingdrmer/openraft that referenced this issue Jun 29, 2023
@drmingdrmer
Fix: restore replication progress when a leader starts up
ef73d53 
As a leader, the replication progress to itself should be restored upon
startup.

And if this leader is the only node in a cluster, it should re-apply all
of the logs to state machine at once.

- Fix: datafuselabs#883
drmingdrmer added a commit that referenced this issue Jun 29, 2023
@drmingdrmer
Fix: restore replication progress when a leader starts up (#884)
86b46a0 
As a leader, the replication progress to itself should be restored upon
startup.

And if this leader is the only node in a cluster, it should re-apply all
of the logs to state machine at once.

- Fix: #883
drmingdrmer added a commit to drmingdrmer/openraft that referenced this issue Nov 28, 2023
@drmingdrmer
Fix: restore replication progress when a leader starts up (datafusela…
c2d55d9 
…bs#884)

As a leader, the replication progress to itself should be restored upon
startup.

And if this leader is the only node in a cluster, it should re-apply all
of the logs to state machine at once.

- Fix: datafuselabs#883
drmingdrmer added a commit to drmingdrmer/openraft that referenced this issue Nov 28, 2023
@drmingdrmer
Fix: restore replication progress when a leader starts up (datafusela…
63e69b9 
…bs#884)

As a leader, the replication progress to itself should be restored upon
startup.

And if this leader is the only node in a cluster, it should re-apply all
of the logs to state machine at once.

- Fix: datafuselabs#883
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix: restore replication progress when a leader starts up drmingdrmer/openraft
1 participant
@drmingdrmer