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

blockstore: mark slot as dead on data shred merkle root conflict #3970

Merged
merged 1 commit into from
Dec 7, 2024

Conversation

AshwinSekar
Copy link

@AshwinSekar AshwinSekar commented Dec 6, 2024

We need to mark the slot as dead to ensure that the bank is completed

@AshwinSekar AshwinSekar changed the title blockstore: always insert conflicting shred after notifying duplicate blockstore: mark slot as dead on data shred merkle root conflict Dec 6, 2024
0,
false,
0,
false, // merkle_variant
Copy link
Author

Choose a reason for hiding this comment

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

this test was broken, legacy shreds are dropped on all clusters

@AshwinSekar AshwinSekar requested a review from carllin December 6, 2024 06:51
@AshwinSekar AshwinSekar merged commit 5564a94 into anza-xyz:master Dec 7, 2024
40 checks passed
@AshwinSekar AshwinSekar deleted the always-insert-shred branch December 11, 2024 16:34
@AshwinSekar AshwinSekar added v2.0 Backport to v2.0 branch v2.1 Backport to v2.1 branch labels Dec 12, 2024
Copy link

mergify bot commented Dec 12, 2024

Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule.

Copy link

mergify bot commented Dec 12, 2024

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.

mergify bot pushed a commit that referenced this pull request Dec 12, 2024
(cherry picked from commit 5564a94)

# Conflicts:
#	ledger/src/blockstore.rs
mergify bot pushed a commit that referenced this pull request Dec 12, 2024
(cherry picked from commit 5564a94)

# Conflicts:
#	ledger/src/blockstore.rs
AshwinSekar added a commit that referenced this pull request Dec 20, 2024
…t (backport of #3970) (#4074)

* blockstore: mark slot as dead on data shred merkle root conflict (#3970)

(cherry picked from commit 5564a94)

# Conflicts:
#	ledger/src/blockstore.rs

* fix conflicts

---------

Co-authored-by: Ashwin Sekar <[email protected]>
Co-authored-by: Ashwin Sekar <[email protected]>
AshwinSekar added a commit that referenced this pull request Dec 20, 2024
…t (backport of #3970) (#4075)

* blockstore: mark slot as dead on data shred merkle root conflict (#3970)

(cherry picked from commit 5564a94)

# Conflicts:
#	ledger/src/blockstore.rs

* fix conflicts

---------

Co-authored-by: Ashwin Sekar <[email protected]>
Co-authored-by: Ashwin Sekar <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v2.0 Backport to v2.0 branch v2.1 Backport to v2.1 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants