-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[VL] Error during spilling: The current running driver and the request driver must be from the same task #6864
Comments
Error call stack:
|
It's probably because one Velox task is extending a vector created in another Velox task. (the call |
Related to facebookincubator/velox#10705 |
#10768) Summary: Add a global bool flag `FLAGS_transferred_arbitration_allowed` (by default `false`), when it is set to `true`, Velox will allow growing a buffer that was created in a different task. This could fix Gluten issue apache/incubator-gluten#6864. Pull Request resolved: #10768 Reviewed By: tanjialiang Differential Revision: D61457781 Pulled By: xiaoxmeng fbshipit-source-id: f8b1b77cf9d5a1d913a77f880b592e2600e8c716
So it's the velox task threads, not Spark's, right? how multiple threads are triggered during spill? |
The two Velox tasks are running on the same Spark thread, though they are created by different #6932 will fix this |
…n another Velox task (apache#6932) Closes apache#6864
Velox has this restriction to disallow spilling one task by operations in another task. We used to follow the restriction in Gluten but somehow we lost it so an error
The current running driver and the request driver must be from the same task
occurs.It's found in a local TPC-DS test.
The text was updated successfully, but these errors were encountered: