hiero-ledger / hiero-ledger/hiero-consensus-node

Make use of virtual hash chunks in reconnects

Open
#24,699 0 comments 0 reactions 0 assignees View on GitHub
Improvement Performance Platform Platform Reconnect Platform Virtual Map
Dominant language
Java
Stars
406
Forks
226
Avg merge
3d 4h
Merged PRs (30d)
210

Description

This is a part of the https://github.com/hiero-ledger/hiero-consensus-node/issues/23970 epic.

Current reconnects are based on individual hashes. Learner provides node hashes to the teacher. Teacher responses if the node is clean or dirty (and includes leaf data for dirty nodes). Recently, hashes have been changed to be stored in chunks on disk. This means, to read multiple hashes in a single chunk, only one disk operation is needed. Reconnects may be improved to leverage this mechanism, on both learner and teacher sides, rather than loading and sending hashes one by one.

Contributor guide

Open the contributing guide

Research direction

Start with epic #23970 and trace the reconnect hash exchange on both learner and teacher sides, then inspect the existing on-disk virtual hash chunk mechanism. Done means reconnects use chunk-based reads and transfers instead of loading and sending hashes one by one; the issue names no specific files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.