Deleting replications results in a timeout #18969
Replies: 1 comment
-
Track this by issue #18988. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey 👋
i want to remove several replications which we used to push images to docker hub for about an year. So the Replication got executed quite often. When i try to delete the replication i always got a timeout for the request so i updated the ingress with in Timeout of 3600s which is fine, but the delete request still never succeeded.
Next i checked the code and found out that the request first looks up all executions for this policy than all tasks for the execution and fails as soon as any of the executions is not in a final state. But i checked this condition in the database and all executions where in a final state. So i counted the executions and there were about 50k tasks that should be deleted.
I guess that the deletion process is taking too much time so that the request never succeeds. Is there a way to improve the speed? I would prefer not to delete the entries from the database by hand.
Beta Was this translation helpful? Give feedback.
All reactions