Description
We currently validate executor settings in the client before submitting a job to the scheduler. The scheduler then passes those settings on to the executor without examining them at all. It would be possible to use the API to directly create tasks without validating the input at all. This could lead to mysterious executor crashes. To address this the executor should validate input as well and FAIL the task right away if invalid settings are found.
Attachments
Issue Links
- is duplicated by
-
AURORA-1552 Perform explicit config validation in the executor when configuring health checker
- Resolved