state.db read connection pool leak and limits
Cluster 98573 · agent. Data as of
Nothing open on GitHub. Fix merged in #98691 on 31 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #98691. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #98691. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address per-thread read connections to state.db that are never closed in long-lived gateway processes, and introduce bounding and reduction of the read connection pool to control file-descriptor usage.
Open issues0
Open PRs0
Fixes on record
-
#98691 fix(state): bound state.db read connections per file, not per SessionDB
files:
gateway/run.py,hermes_state.py,tests/gateway/test_session_db_handle_sharing.py,tests/test_session_db_read_conn_pool.py
1 PR closed without merging
From the close comments: other 1
-
#98585 fix(state): reduce _READ_POOL_MAX 8→4 to halve peak state.db file-descriptor budget · other →
#98573
Closed issues · 1
- Closed#98573long-lived gateway holds ~20 state.db handles per process; per-thread read connections are never released
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Merged PRs
- #98691
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 31 Aug 2026