Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,6 @@ public void setVolumePaths(List<String> volumePaths) {

@Override
public boolean executeInSequence() {
return true;
return false;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmsperu is this relevant?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DaanHoogland yes — this is the change that allows the parallel execution the PR title describes. With executeInSequence returning true (the previous default for TakeBackupCommand), the KVM agent serialises any other backup commands behind it; a long-running snapshot copy would block a concurrent delete on a different VM's backup. Flipping it to false lets the agent dispatch DeleteBackupCommand immediately alongside an in-flight TakeBackupCommand, which is the whole point of #12847.

The safety case is bounded — the backup and delete operations target different on-NAS paths (each backup is named after its VM uuid + timestamp), so there's no path-level contention to worry about, and the NFS mount lifecycle is per-script-invocation, not shared. Happy to add an inline comment in TakeBackupCommand.java noting this if you'd like that documented at the class level.

}
}
Loading