-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[BUG] Can't delete runs with mlflow gc due to api timeout #12005
Comments
@darrenjkt Can you run |
Running the
|
@darrenjkt To confirm, you're running both |
Yes that's correct |
@darrenjkt can you log artifacts? |
Yes I can. I usually log my artifacts from a separate mflow client to the |
@darrenjkt What happens on you set |
When I do that, I get this error |
@darrenjkt Thanks for trying. Do you see any logs in the tracking server? When 500 (internal error) occurs, tracking server usually prints out a traceback or error messages. |
Ah thanks I got the following error in the tracking server logs related to permissions on my AWS user.
However, I've set up a user with AmazonRDSFullAccess and AmazonS3FullAccess but yet I still get this error. The user has DeleteObject permissions for S3. |
Solved it! I was exporting the AWS keys in the local environment but starting the mlflow server with a different set of AWS keys. Starting the mlflow server using the AWS keys with correct permissions resolved the gc deletion issue. Thanks for your help! |
Issues Policy acknowledgement
Where did you encounter this bug?
Local machine
Willingness to contribute
No. I cannot contribute a bug fix at this time.
MLflow version
System information
Describe the problem
I am trying to permanently delete a single run with the gc command.
I am hosting the mlflow server with the command:
I have set up the environment variable:
export MLFLOW_TRACKING_URI=http://0.0.0.0:4242
Tracking information
No response
Code to reproduce issue
Stack trace
Other info / logs
No response
What component(s) does this bug affect?
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/deployments
: MLflow Deployments client APIs, server, and third-party Deployments integrationsarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/recipes
: Recipes, Recipe APIs, Recipe configs, Recipe Templatesarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingWhat interface(s) does this bug affect?
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportWhat language(s) does this bug affect?
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesWhat integration(s) does this bug affect?
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsThe text was updated successfully, but these errors were encountered: