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
When a Node Plugin implements the STAGE_UNSTAGE volume capability, we need to do some local state tracking on the client to only call NodeUnstageVolume when the last allocation that uses the volume shuts down.
This means that we need to keep a track of running allocations for a given volume and then only call NodeUnstageVolume during UnmountVolume when freeing the volume.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
When a Node Plugin implements the
STAGE_UNSTAGE
volume capability, we need to do some local state tracking on the client to only callNodeUnstageVolume
when the last allocation that uses the volume shuts down.This means that we need to keep a track of running allocations for a given volume and then only call
NodeUnstageVolume
duringUnmountVolume
when freeing the volume.The text was updated successfully, but these errors were encountered: