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
If the execution fails for some reason (bug in the pipeline), the mlflow run is not closed. This creates unintended side effects: for instance, if you rerun the pipeline, the new run will be nested in the failing runs and the mllflow database will become very messy.
This bug does not occur when running from the command line since the mlflow run is automatically closed when exiting.
Context
Today, you can execute a kedro pipeline interactively. The logic would be to load the context, and then to run the pipeline.
Description
If the execution fails for some reason (bug in the pipeline), the mlflow run is not closed. This creates unintended side effects: for instance, if you rerun the pipeline, the new run will be nested in the failing runs and the mllflow database will become very messy.
This bug does not occur when running from the command line since the mlflow run is automatically closed when exiting.
Possible Implementation
Implement a
on_pipeline_error
kedroHook
to close the mlflow run when the pipeline fails.The text was updated successfully, but these errors were encountered: