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

TSS mode: logs not moving after "HintsControllerImpl - Voting for own preprocessed keys".

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

Description

CN version=v0.73.0-rc.4
CN hgcaa.log is not progressing after the lines:

`HintsControllerImpl - Voting for own preprocessed keys`.

(Logs https://perf.analytics.eng.hashgraph.io/ephemeral/test_runs/v0.73.0-rc.4_AdHoc5_727/solo_deploy/podlog_solo-sdpt-n5/network-node1_logs/)

hence Solo deployment cannot detect TSS readiness statement and fails by timeout, e.g.:
https://github.com/hiero-ledger/hiero-consensus-node/actions/runs/24351720366/job/71107734063#step:41:544

Jstack report of such CN state: https://perf.analytics.eng.hashgraph.io/ephemeral/test_runs/v0.73.0-rc.4_AdHoc5_727/solo_deploy/podlog_solo-sdpt-n5/network-node1_logs/jstack.txt

Be advised, this step is OK with CN 'main'

Contributor guide

Open the contributing guide

Research direction

Start with the linked hgcaa.log and jstack.txt for the v0.73.0-rc.4 Solo deployment, focusing on the state after “HintsControllerImpl - Voting for own preprocessed keys.” Compare that behavior with CN main, then trace the TSS readiness detection and timeout shown in the linked GitHub Actions job. Done means the logs progress and Solo detects TSS readiness without timing out.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, cryptography, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.