You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In internal experiments, we observed that an Acero plan with use_threads=false may not fully respond to an interruption. In this case, even though the signal is handled, the source nodes continue to push batches until done. Part of this issue is to devise testing for this condition.
Component(s)
C++
The text was updated successfully, but these errors were encountered:
…false` (#35953)
### What changes are included in this PR?
The execution plan set-up code is refactored to call `StopProducing` on the plan in the reader's `Close`. Originally, `StopProducing` was called from the destructor of `BatchConverter`, but with `use_threads=false` a hang occurs prior to this point in the code.
### Are these changes tested?
Yes - a test that early-closes a plan reader.
### Are there any user-facing changes?
Yes; this will fix a hang visible to users.
* Closes: #35935
Lead-authored-by: Yaron Gvili <rtpsw@hotmail.com>
Co-authored-by: rtpsw <rtpsw@hotmail.com>
Signed-off-by: Li Jin <ice.xelloss@gmail.com>
Describe the enhancement requested
In internal experiments, we observed that an Acero plan with
use_threads=false
may not fully respond to an interruption. In this case, even though the signal is handled, the source nodes continue to push batches until done. Part of this issue is to devise testing for this condition.Component(s)
C++
The text was updated successfully, but these errors were encountered: