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

remove LogEntry #8

Open
jinyuttt opened this issue Nov 8, 2023 · 1 comment
Open

remove LogEntry #8

jinyuttt opened this issue Nov 8, 2023 · 1 comment

Comments

@jinyuttt
Copy link

jinyuttt commented Nov 8, 2023

remove LogEntry？
@hhblaze
Copy link
Owner

hhblaze commented Nov 8, 2023

If you remove logEntry newly connected peers will not be able to restore the state of the database, nobody knows which peer will be chosen as a restoration point, so each peer should have it. Nevertheless, it is a point of optimization. Because LogEntry is a DBreeze table, it is possible to stop instance, to make records more compact, zip it and transfer as a file (table files) to the new peer. This RAFT.NET implementation is a basic point that can grow in any direction depending upon the needs.

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

No branches or pull requests
2 participants
@hhblaze @jinyuttt