-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
merge window and ledger #1717
Milestone
Comments
Closed
This was referenced Nov 29, 2018
vkomenda
pushed a commit
to vkomenda/solana
that referenced
this issue
Aug 29, 2021
…olana-labs#1717) Bumps [@solana/web3.js](https://github.com/solana-labs/solana-web3.js) from 1.9.1 to 1.10.1. - [Release notes](https://github.com/solana-labs/solana-web3.js/releases) - [Changelog](https://github.com/solana-labs/solana-web3.js/blob/master/.releaserc.json) - [Commits](solana-labs/solana-web3.js@v1.9.1...v1.10.1) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
brooksprumo
pushed a commit
to brooksprumo/solana
that referenced
this issue
Jun 13, 2024
gregcusack
pushed a commit
to gregcusack/solana
that referenced
this issue
Jun 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
A ledger and window keyed by entry_height does not accommodate forks or the skip-list form of the ledger as transmitted by rotating leaders.
Proposed Solution
Move ledger and window to rocksdb, keyed by <leader_period, index> where index is relative to the leader period. The db should persist blobs directly in order to retain the signatures of the leaders for repair responses.
This effectively merges window and ledger.
Replicate stage and repair would/could be moved to consuming the ledger directly instead of consuming deserialized vectors of Entries.
The TVU's ledger_write_stage goes away.
Deserialization from the ledger moves to replicate stage (I think).
The text was updated successfully, but these errors were encountered: