Push MLflow experiment tracking to a reconciler to avoid race conditions #135
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mliu-cloudera
changed the title
mliu-cloudera
approved these changes
Feb 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(tl;dr of this Slack message)
RAG Studio tracks session metrics (#124) and data source metrics (#125) in their own experiments. However, CML's MLflow tracking store relies on global environmental state, and makes it impossible for us to run multiple MLflow experiments in parallel in CDSW.
So to keep RAG Studio's ability to serve asynchronous requests, we're pushing MLflow experiment tracking operations to a reconciler that can process one experiment run at a time on the side—without blocking the server.