[Feature Request]: Add log warnings for deadlock prevention
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 216
Description
### What would you like to happen?
It would be useful to add some log messages when a transform fills its Input Buffer, but can't empty its Output Buffer (tipical symptom of a deadlock).
You can actually notice this if you're executing a pipeline in Hop GUI, but can't tell this so easily if you're running in a non-graphical environment (e.g. Hop Run), or even if the deadlocked pipeline happens to be a "nested" one (injected pipelines and sub-pipelines are not well traced even in Hop GUI).
### Issue Priority
Priority: 3
### Issue Component
Component: Hop Run, Component: Pipelines, Component: Transforms, Component: Hop Gui
Contributor guide
Research direction
Start by tracing how pipeline transforms detect a full Input Buffer alongside an uncleared Output Buffer, then check how Hop Run and Hop GUI currently surface pipeline state. Done means a useful warning is emitted for this condition, including enough context to identify the affected transform in non-graphical and nested pipelines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100