-
Notifications
You must be signed in to change notification settings - Fork 5
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
detect and clearly report OOM error and improve python UDF error reporting #890
Comments
A case coming from support: r-2502141707054cd4b2d662309d86b12e Very relevant logging also: This suggests we need to add something right here:
Full stack trace:
|
Might be good to suggest user to double check memory settings after an
|
I had a batch job with these final errors in the editor log viewer:
Previous errors were very clear:
It should really be possible to detect these errors, and as a final message, give the advice to increate executor-memory.
Example job: j-2410038ebc994cb9a485ee653e1136cb
The text was updated successfully, but these errors were encountered: