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

[bug] Execution not caching #5762

Closed
Itega opened this issue May 31, 2021 · 4 comments
Closed

[bug] Execution not caching #5762

Itega opened this issue May 31, 2021 · 4 comments
Labels
lifecycle/stale The issue / pull request is stale, any activities remove this label.

Comments

@Itega
Copy link

Itega commented May 31, 2021

What steps did you take:

What happened:

The sample failed with error :
RuntimeError: The cached execution was not re-used or pipeline run took to long to complete.

What did you expect to happen:

The sample should have run successfully.

Environment:

Kubernetes : 1.18.18-gke.1100
KFP version : 1.6.0
KFP SDK version: 1.6.2

@Bobgy
Copy link
Contributor

Bobgy commented Jun 3, 2021

@Ark-kun is this sample still working properly?
It fails in our test infra too:
https://testgrid.k8s.io/googleoss-kubeflow-pipelines#kubeflow-pipeline-postsubmit-integration-test

@Itega
Copy link
Author

Itega commented Jun 3, 2021

I can give you more information about my case as I have now found a way to install KFP 1.6 with caching on GCP.
My problem was that I was using a GKE private cluster, I tried with a public cluster and it's working fine.
Did some search and Kubeflow does not seems to be compatible with private cluster on GKE : GoogleCloudPlatform/kubeflow-distribution#267 Maybe you have more informations on this ?

Can confirm the sample is working well on my public cluster so I really think there is a problem with caching on some Kubernetes cluster configurations.

@stale
Copy link

stale bot commented Sep 3, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Sep 3, 2021
@stale
Copy link

stale bot commented Mar 3, 2022

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

@stale stale bot closed this as completed Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale The issue / pull request is stale, any activities remove this label.
Projects
None yet
Development

No branches or pull requests

2 participants