Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Because of ofs:// filesystem hierarchy starts with volume then bucket, an application typically won't be able to write directly under a first-level folder, e.g. ofs://service-id1/tmp/. /tmp/ is a special case that we need to handle since that is the default location most legacy Hadoop applications write to for swap/temporary files. In order to address this, we would introduce /tmp/ as a client-side "mount" to another Ozone bucket.
Note that the preliminary implementation would only allow for /tmp/ to be a mount but not any user-defined path.
Attachments
Issue Links
- causes
-
HDDS-5801 ofs temp implementation different from design doc
- Open
- links to