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

[pruner] keep state of last manually processed SST files #15926

Conversation

phoenix-o
Copy link
Contributor

PR introduces state tracking for the last manually processed SST files in memory. This prevents the recurrence of situations where the same file is repeatedly selected for manual compaction because its initial compaction run was a noop.
Cherry pick is required to unblock partners full node.

Copy link

vercel bot commented Jan 25, 2024

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

Name Status Preview Comments Updated (UTC)
mysten-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 26, 2024 4:14pm
sui-core ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 26, 2024 4:14pm
sui-typescript-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 26, 2024 4:14pm
3 Ignored Deployments
Name Status Preview Comments Updated (UTC)
explorer ⬜️ Ignored (Inspect) Visit Preview Jan 26, 2024 4:14pm
multisig-toolkit ⬜️ Ignored (Inspect) Visit Preview Jan 26, 2024 4:14pm
sui-kiosk ⬜️ Ignored (Inspect) Visit Preview Jan 26, 2024 4:14pm

@ebmifa
Copy link
Contributor

ebmifa commented Jan 25, 2024

@phoenix-o Does this have to be part of the v1.17.0 release next week?

@phoenix-o
Copy link
Contributor Author

@ebmifa: ideally, yes. The fix is requested by Bybit

…15921)

PR introduces state tracking for the last manually processed SST files
in memory. This prevents the recurrence of situations where the same
file is repeatedly selected for manual compaction because its initial
compaction run was a noop
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.

2 participants