Details
-
Technical task
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
-
9223372036854775807
Description
This ticket tracks the rename() support for WBC.
The rename() operation uses a strategy similar to hardlink() operation. It deroots the parent inodes first, and then synchronizes them to the metadata server to perform the rename() operation. Nevertheless, we can do some optimization for rename() operation under WBC: if the parent directory of the source file and the target file are both in the state flagged with Complete (C) and not Flushed ( ̃F), the client can directly perform the rename() operation locally in MemFS.