hiero-ledger / hiero-ledger/hiero-consensus-node
ISS Debugging with Blocks
- Dominant language
- Java
- Stars
- 406
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
Background Information can be found [here](https://github.com/hashgraph/hedera-block-node/issues/363).
The purpose of this epic is to provide ISS debugging information that is easily accessible to developers. After Mega Map is implemented, the only useful information for debugging ISSes will be the block data for the round that had the ISS. To get this data, these steps should be taken:
1. Platform notifies the application when an ISS has occurred and for what round.
2. The application locates the block for the associated round.
3. The application uploads that block to a GCP bucket.
This process is temporary because the long term plan is to move ISS detection to the application layer and this extra platform-app communication will no longer be needed. Until that point, we can use the NotificationEngine to achieve step 1.
```[tasklist]
### Tasks
- [ ] https://github.com/hashgraph/hedera-services/issues/17266
- [ ] https://github.com/hashgraph/hedera-services/issues/17267
```
Contributor guide
Research direction
Start with the background issue and the linked tasks 17266 and 17267, then read the NotificationEngine context described here. Trace how an ISS notification can identify its round and how the application can locate and upload that round's block to a GCP bucket. Done means both task issues are completed and the ISS debugging block data is accessible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, java
- Domain
- cloud, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100