You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some Spark jobs are idempotent and can be resubmitted without problems especially if they fail due to external constraints (like endpoints not being ready and such)
The user should be able to configure such jobs with a restart policy.
The text was updated successfully, but these errors were encountered:
That requires spark.ui to be true right? Anyway, establishing the status of the job (for batch jobs) is not the problem (it's currently solved). The user has to specify whether restarting the job is safe or not.
For streaming jobs, we might want indeed to use a Deployment instead of a Job for the spark-submitPod.
Description
Some Spark jobs are idempotent and can be resubmitted without problems especially if they fail due to external constraints (like endpoints not being ready and such)
The user should be able to configure such jobs with a restart policy.
The text was updated successfully, but these errors were encountered: