andygrove opened a new issue, #2840: URL: https://github.com/apache/datafusion-ballista/issues/2840
Follow-up from #2721. Under push-staged scheduling, when a task cannot be prepared the job's status only says "task could not be prepared or was rejected by executor", and the actual reason is only in the scheduler's log. Pull-staged scheduling puts the reason in the status. This applies to every task-preparation failure, but #2721 makes one of them an expected, user-facing error: a stage split between tasks that holds a leaf the scheduler cannot restrict now fails with a message that names the node and what to implement. Users on push-staged scheduling don't see that message. The job status should carry the reason, as it does under pull-staged scheduling. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
