You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched in the issues and found no similar issues.
What would you like to be improved?
when release the optimizer, the amoro will remove the resource in the and then remove the instance
when the optimizer expired, the amoro will remove the instance and will not remove resouce in the db, which will cause this dirty data,
How should we improve?
we should flow the step when release the optimzier, when we detect the optimizer instance expired, not only should we remove the optimzier, we also should remove the resource record in the db
Search before asking
What would you like to be improved?
when release the optimizer, the amoro will remove the resource in the and then remove the instance
when the optimizer expired, the amoro will remove the instance and will not remove resouce in the db, which will cause this dirty data,
How should we improve?
we should flow the step when release the optimzier, when we detect the optimizer instance expired, not only should we remove the optimzier, we also should remove the resource record in the db
Are you willing to submit PR?
Subtasks
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: