Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add GCS token refresh for log_artifacts #13397

Merged
merged 13 commits into from
Oct 18, 2024

Conversation

kriscon-db
Copy link
Collaborator

@kriscon-db kriscon-db commented Oct 11, 2024

🛠 DevTools 🛠

Open in GitHub Codespaces

Install mlflow from this PR

pip install git+https://github.com/mlflow/mlflow.git@refs/pull/13397/merge

Checkout with GitHub CLI

gh pr checkout 13397

Related Issues/PRs

#xxx

What changes are proposed in this pull request?

Added GCP token refresh attempt to log_artifacts in the gcs_artifact_repo

How is this PR tested?

  • Existing unit/integration tests
  • New unit/integration tests
  • Manual tests

Unit test added, updated existing tests, and verified on a GCP workspace that the refresh works to get a large model registered.

Does this PR require documentation update?

  • No. You can skip the rest of this section.
  • Yes. I've updated:
    • Examples
    • API references
    • Instructions

Release Notes

Is this a user-facing change?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

  • area/artifacts: Artifact stores and artifact logging
  • area/build: Build and test infrastructure for MLflow
  • area/deployments: MLflow Deployments client APIs, server, and third-party Deployments integrations
  • area/docs: MLflow documentation pages
  • area/examples: Example code
  • area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
  • area/models: MLmodel format, model serialization/deserialization, flavors
  • area/recipes: Recipes, Recipe APIs, Recipe configs, Recipe Templates
  • area/projects: MLproject format, project running backends
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • area/server-infra: MLflow Tracking server backend
  • area/tracking: Tracking Service, tracking client APIs, autologging

Interface

  • area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  • area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
  • area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
  • area/windows: Windows support

Language

  • language/r: R APIs and clients
  • language/java: Java APIs and clients
  • language/new: Proposals for new client languages

Integrations

  • integrations/azure: Azure and Azure ML integrations
  • integrations/sagemaker: SageMaker integrations
  • integrations/databricks: Databricks integrations

How should the PR be classified in the release notes? Choose one:

  • rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • rn/feature - A new user-facing feature worth mentioning in the release notes
  • rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
  • rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

Yes should be selected for bug fixes, documentation updates, and other small changes. No should be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.

What is a minor/patch release?
  • Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
    Bug fixes, doc updates and new features usually go into minor releases.
  • Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
    Bug fixes and doc updates usually go into patch releases.
  • Yes (this PR will be cherry-picked and included in the next patch release)
  • No (this PR will be included in the next minor release)

@github-actions github-actions bot added area/artifacts Artifact stores and artifact logging rn/none List under Small Changes in Changelogs. labels Oct 11, 2024
Copy link

github-actions bot commented Oct 11, 2024

Documentation preview for 81681b5 will be available when this CircleCI job
completes successfully.

More info

Copy link

@kriscon-db Thank you for the contribution! Could you fix the following issue(s)?

⚠ DCO check

The DCO check failed. Please sign off your commit(s) by following the instructions here. See https://github.com/mlflow/mlflow/blob/master/CONTRIBUTING.md#sign-your-work for more details.

@kriscon-db kriscon-db requested review from harupy and artjen October 13, 2024 01:41
@kriscon-db
Copy link
Collaborator Author

/autoformat

@kriscon-db kriscon-db requested a review from artjen October 15, 2024 23:41
mlflow/store/artifact/gcs_artifact_repo.py Outdated Show resolved Hide resolved
mlflow/store/artifact/gcs_artifact_repo.py Outdated Show resolved Hide resolved
Comment on lines 119 to 124
_logger.info(
"Failed to complete upload request, possibly due to credential expiration."
f" Attempting to refresh credentials and trying again... (Error: {e})"
)
if self.credential_refresh_def is not None:
new_token = self.credential_refresh_def()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
_logger.info(
"Failed to complete upload request, possibly due to credential expiration."
f" Attempting to refresh credentials and trying again... (Error: {e})"
)
if self.credential_refresh_def is not None:
new_token = self.credential_refresh_def()
if self.credential_refresh_def is not None:
_logger.info(
"Failed to complete upload request, possibly due to credential expiration."
f" Attempting to refresh credentials and trying again... (Error: {e})"
)
new_token = self.credential_refresh_def()

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This logger message is to indicate that we failed due to a potential credential expiration and that we are attempting to refresh again. I don't think it should be in the if block.

@kriscon-db kriscon-db requested review from artjen and harupy October 17, 2024 01:54
@kriscon-db
Copy link
Collaborator Author

/autoformat

provided by creds_func.
"""
try:
first_creds = creds_func() if orig_creds is None else orig_creds
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there any chance that creds_func() throws?

Copy link
Collaborator Author

@kriscon-db kriscon-db Oct 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes but that would be a UC error and we should just fail the upload at that point on subsequent retries.

return {
"oauth_token": new_gcp_creds.oauth_token,
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to return a dict? can we return new_gcp_creds.oauth_token?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is to match the pattern for credential refresh for other repositories.

@kriscon-db kriscon-db force-pushed the gcp_credential_refresh branch from 3c483f9 to 72d8c88 Compare October 17, 2024 23:05
@kriscon-db
Copy link
Collaborator Author

/autoformat

@kriscon-db kriscon-db merged commit 0862ba2 into mlflow:master Oct 18, 2024
40 checks passed
serena-ruan pushed a commit to serena-ruan/mlflow that referenced this pull request Oct 25, 2024
Signed-off-by: mlflow-automation <[email protected]>
Co-authored-by: mlflow-automation <[email protected]>
serena-ruan pushed a commit to serena-ruan/mlflow that referenced this pull request Oct 25, 2024
Signed-off-by: mlflow-automation <[email protected]>
Co-authored-by: mlflow-automation <[email protected]>
serena-ruan pushed a commit that referenced this pull request Oct 25, 2024
Signed-off-by: mlflow-automation <[email protected]>
Co-authored-by: mlflow-automation <[email protected]>
karthikkurella pushed a commit to karthikkurella/mlflow that referenced this pull request Jan 30, 2025
Signed-off-by: mlflow-automation <[email protected]>
Co-authored-by: mlflow-automation <[email protected]>
Signed-off-by: k99kurella <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/artifacts Artifact stores and artifact logging rn/none List under Small Changes in Changelogs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants