[Feature]: dump current requests on failure or on SIGKILL
@laikhtewari is already working on this.
Since Jan 27, 2026.
- Dominant language
- Python
- Stars
- 14.7k
- Forks
- 2.8k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 489
Description
🚀 The feature, motivation and pitch
When using TRT-LLM in production it occasionally may crash or hang from some request combinations. However, it is currently very hard to reproduce such failures, because there is no way to learn, which requests were in the batch, when such a crash happened.
I propose adding a config parameter to enable dumping the current requests to a file, that would be triggered in the events of crashes, and when the external system is killing the worker due to it failing the health checks.
cc @ltalal
Alternatives
Setting up a proxy, which is fully aware of all the states of all the requests being executed on all the instances.
Additional context
No response
Before submitting a new issue...
- Make sure you already searched for relevant issues, and checked the documentation and examples for answers to frequently asked questions.
Contributor guide
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.
Assessment
This issue has not been assessed yet.