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
4 changes: 4 additions & 0 deletions pkg/ddc/alluxio/ufs_internal.go
Original file line number Diff line number Diff line change
Expand Up @@ -145,6 +145,10 @@ func (e *AlluxioEngine) FindUnmountedUFS() (unmountedPaths []string, err error)
return fileUtils.FindUnmountedAlluxioPaths(alluxioPaths)
}

// processUpdatingUFS updates the under file system (UFS) mount configuration for the Alluxio engine.
// It first determines the update method based on whether mount config map is enabled,
// then if the update succeeds, it resets the dataset's UfsTotal status to trigger a metadata sync,
// and finally updates the mount timestamp when new mount paths are added.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Small wording nit on this new doc comment: it jumps from "resets the dataset's UfsTotal status to trigger a metadata sync" straight to updating the mount timestamp, but the function actually invokes SyncMetadata explicitly after the status reset, and only then calls updateMountTime (and only when ufsToUpdate.ToAdd() is non-empty). Could you tweak the last sentence to call out SyncMetadata so the doc stays aligned with the control flow? For example: "...resets the dataset's UfsTotal status to Calculating, invokes SyncMetadata, and finally updates the mount timestamp when new mount paths have been added."

func (e *AlluxioEngine) processUpdatingUFS(ufsToUpdate *utils.UFSToUpdate) (updateReady bool, err error) {
dataset, err := utils.GetDataset(e.Client, e.name, e.namespace)
if err != nil {
Expand Down
Loading