-
Notifications
You must be signed in to change notification settings - Fork 242
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
[FEA] Support retry on the driver side #11980
Comments
There are two parts to this function (
|
Thx for the info, close this.
Error stack
It is a random issue. The test will pass if running them separately. And the failing tests vary from run to run, but all are caused by NPE. So I guess this would be related to the order of task context initialization and calling the
|
Is your feature request related to a problem? Please describe.
[Not sure if this is a must-have feature request, but still filed for discussion.]
This is relevant to #11979.
Some calls to
getColumnarBatch
will happen on the driver side, e.g. reading a host batch for broadcasting. Not sure if we need to protect these calls by a retry block. If yes, then we need to support retry on the driver side.Describe the solution you'd like
Current retry requires a task id to work, maybe we can introduce some special task IDs for the driver threads.
The text was updated successfully, but these errors were encountered: