Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

image.png

*Hello,*
We noticed that many jobs have been stuck in the *ABORTING* state for several hours. This happened after we deleted them using `flytectl`, following a period where *Propeller was overloaded*.
After increasing Propeller’s resources, some of the *pending jobs completed successfully* and some ABORTING jobs transitioning to the *ABORTED* state. However, a large number of jobs still remain stuck in the *ABORTING* phase.

Potentially a totally separate issue, but I wanted to flag this issue we had where a job was stuck in ABORTING state and was overloading flytepropeller w/ logs just in case it's the same: <https://flyte-org.slack.com/archives/CP2HDHKE1/p1746866294277679>

Should be different. One thing observed is, if we abort job which is still in unknown state, then it is ending up in aborting state