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

Implement a count up latch paradigm with a managed blocker

Open
#11,050 1 comment 0 reactions 0 assignees View on GitHub
Good First Issue Candidate Platform
Dominant language
Java
Stars
406
Forks
226
Avg merge
3d 4h
Merged PRs (30d)
210

Description

The class `CountUpLatch` is fine when using normal threads, but doesn't fit with a fork join pool model. It is unwise to ever block in a fork join pool, since you effectively reduce the maximum concurrency by 1 when you do so. We should create a class with similar properties as `CountUpLatch`, except with a managed blocker pattern.

Contributor guide

Open the contributing guide

Research direction

Start by locating the existing CountUpLatch class and its usages, then inspect how fork join pool tasks are handled in the repository. Compare the required managed blocker pattern with CountUpLatch's behavior; done means a similar count-up latch can be used without directly blocking fork join pool workers.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.