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
A fabric slice that creates an aws dx connection using al2s can expire and is not able to delete the dx connection since it still in use. This falls into the general problem of fabric control framework "leaking resources" .... Fabric should have a way to retry post deleting a slice .... I know the team spoke about this. Just not sure if this has been taken care of or not.
The text was updated successfully, but these errors were encountered:
In the current case, Network AM retries 3 times on failure to delete. If retry attempts also fail an audit process has been added which periodically attempts to clean up the leaked slivers every hour.
I need to check if AL2S handler has 3 retries in built or not.
A fabric slice that creates an aws dx connection using al2s can expire and is not able to delete the dx connection since it still in use. This falls into the general problem of fabric control framework "leaking resources" .... Fabric should have a way to retry post deleting a slice .... I know the team spoke about this. Just not sure if this has been taken care of or not.
The text was updated successfully, but these errors were encountered: