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

[Consensus 2.0] register failure points for new consensus for simtests #17275

Merged
merged 4 commits into from
Apr 24, 2024

Conversation

akichidis
Copy link
Contributor

@akichidis akichidis commented Apr 22, 2024

Description

  • Adds failure points for new consensus
  • Verify commits timestamp monotonicity and panics if that fails

Test plan

CI


Release notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.

For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

  • Protocol:
  • Nodes (Validators and Full nodes):
  • Indexer:
  • JSON-RPC:
  • GraphQL:
  • CLI:
  • Rust SDK:

Copy link

vercel bot commented Apr 22, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sui-core ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 24, 2024 10:14am
3 Ignored Deployments
Name Status Preview Comments Updated (UTC)
multisig-toolkit ⬜️ Ignored (Inspect) Visit Preview Apr 24, 2024 10:14am
sui-kiosk ⬜️ Ignored (Inspect) Visit Preview Apr 24, 2024 10:14am
sui-typescript-docs ⬜️ Ignored (Inspect) Visit Preview Apr 24, 2024 10:14am

Copy link
Member

@mwtian mwtian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything else looks good, except I don't think commit timestamp enforces monotonicity at creation. Let me fix that in another PR first.

Copy link
Contributor

@arun-koshy arun-koshy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice changes!

@@ -37,6 +37,8 @@ pub(crate) struct CommitObserver {
sender: UnboundedSender<CommittedSubDag>,
/// Persistent storage for blocks, commits and other consensus data.
store: Arc<dyn Store>,
/// The last committed sub dag
last_sub_dag: Option<CommittedSubDag>,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: instead of keeping the entire last committed subdag in memory what if we just kept the commit index + timestamp?

@akichidis akichidis force-pushed the akichidis/consensus-failure-points branch from 3223d18 to 4e769a6 Compare April 24, 2024 10:13
@akichidis akichidis merged commit 1293197 into main Apr 24, 2024
46 of 47 checks passed
@akichidis akichidis deleted the akichidis/consensus-failure-points branch April 24, 2024 11:05
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.

3 participants