n0-computer / n0-computer/iroh-docs
Iroh aborts under high load
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 74
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
@ppodolsky on discord:
Well... I have left Iroh for the last night and it has been supposed to do intense inserts into docs, but unfortunately I have noted right now that after the last code update Iroh has started to restart sometimes. Looks like process being aborted, no any useful log lines and signs of disruption before abortion. And Iroh has restarted for 4 times in 8 hour period, I have never met these behaviour before latest commits.
I will try to watch Iroh today, but no idea where should I look at.
btw, there is also an intense spam 2024-06-28T04:28:32.076983Z INFO poll_send:get_send_addrs: new connection type typ=mixed me=yyy node=xxx, approximately every second. Mentioned node xxx is always the same
Possibly related to the changes we have made to tokio task handling. I have improved error logging in https://github.com/n0-computer/iroh/pull/2423 already.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported high-load document insert workload and inspect the repeated poll_send:get_send_addrs connection messages. Start with the Tokio task-handling changes and the improved error logging in PR #2423; done means identifying why the process aborts and validating that it no longer restarts under the reported load.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100