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

Updated README and removed an erroneous assert #284

Merged
merged 1 commit into from
Nov 19, 2024
Merged

Conversation

etremel
Copy link
Contributor

@etremel etremel commented Nov 19, 2024

The README section on configuration files was out-of-date, and still referred to the old "leader_ip" and "leader_port" options which no longer exist. I fixed it and added an explanation of the new "per-node config" feature (derecho_node.cfg), which was also missing.

Also, I noticed while testing that an assert in persistence_manager could actually fail during correct behavior, because I misunderstood the invariants of persistence requests and persist() calls. It's possible for persisted_version to be less than the parameter version, if the parameter version corresponds to a null message (which does not create a log entry). When a persistence request is posted, the argument version is just the current version at the time the request was posted, not the latest non-null version; thus it's not true that persist() will always persist up to the persistence request's parameter version.

The README section on configuration files was out-of-date, and still
referred to the old "leader_ip" and "leader_port" options which no
longer exist. I fixed it and added an explanation of the new "per-node
config" feature (derecho_node.cfg), which was also missing.

Also, I noticed while testing that an assert in persistence_manager
could actually fail during correct behavior, because I misunderstood the
invariants of persistence requests and persist() calls. It's possible
for persisted_version to be less than the parameter version, if the
parameter version corresponds to a null message (which does not create a
log entry). When a persistence request is posted, the argument version
is just the current version at the time the request was posted, not the
latest non-null version; thus it's not true that persist() will always
persist up to the persistence request's parameter version.
@etremel etremel merged commit cbac5e0 into master Nov 19, 2024
1 check failed
@etremel etremel deleted the documentation_update branch February 4, 2025 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant