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

Investigate better lifecycle of SimulatedGossip

Open
#21,571 0 comments 0 reactions 0 assignees View on GitHub
Otter
Dominant language
Java
Stars
406
Forks
226
Avg merge
3d 4h
Merged PRs (30d)
210

Description

The lifecycle of `SimulatedGossip` is controlled by `SimulatedNetwork`. This feels unnatural as the `Gossip` functionality is usually part of the node. It is also not entirely clear what happens with the `SimulatedGossip` wires when a node is restarted (i.e., destroyed and recreated).

We should investigate if this can be changed. `SimulatedGossip` should be created and destroyed with its node, and it should be registered and unregistered with `SimulatedNetwork`.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the lifecycle of SimulatedGossip through SimulatedNetwork, including what happens when a node is destroyed and recreated. Done means determining whether SimulatedGossip can be created and destroyed with its node while being registered and unregistered with SimulatedNetwork, with restart behavior understood.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.