Skip to content

Conversation

@mwtian
Copy link
Contributor

@mwtian mwtian commented Jan 30, 2026

Description

Use periodic sync as the fallback when commit sync is not progressing for various reasons.

Test plan

CI

@mwtian mwtian requested a review from a team as a code owner January 30, 2026 17:02
@vercel
Copy link

vercel bot commented Jan 30, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sui-docs Ready Ready Preview, Comment Jan 30, 2026 6:28pm
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
multisig-toolkit Ignored Ignored Preview Jan 30, 2026 6:28pm
sui-kiosk Ignored Ignored Preview Jan 30, 2026 6:28pm

Request Review

Copy link
Contributor

@akichidis akichidis left a comment

Choose a reason for hiding this comment

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

I am approving but I would suggest giving this a good test before rollout.

Comment on lines +919 to +920
// However, if local commit index has not progressed for too long, we run periodic sync anyway to help unblock progress, in case large commit sync
// requests are failing too frequently.
Copy link
Contributor

Choose a reason for hiding this comment

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

Have we actually observed this in any of our environments? Because I would expect this to not significantly help and maybe even create some race between the synchronizer and commit syncer

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes I have observed this in tests where sometimes commit sync took a long time. Let me optimize and test it out a bit more.

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