[
https://issues.apache.org/jira/browse/HDDS-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756202#comment-17756202
]
Siyao Meng commented on HDDS-3545:
----------------------------------
I think we create dummy directory entries for OBS/LEGACY buckets now (when
{{ozone.om.enable.filesystem.paths}} is on?). In this case it should allow
{{fs.getModificationTime()}} to work as intended. Need to check again.
For FSO this shouldn't be a problem at all.
cc [~weichiu] [~erose]
> MR Jobhistory cannot work well with o3fs hadoop compatible file system
> ----------------------------------------------------------------------
>
> Key: HDDS-3545
> URL: https://issues.apache.org/jira/browse/HDDS-3545
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Filesystem
> Reporter: Baolong Mao
> Priority: Major
>
> After take a look at the code of JobHistory, i see jobhistory use
> `fs.getModificationTime()` to get the directory modification time, and use it
> as a condition of starting scan the job directories.
> But, for ozone, wile insert a child to a `directory`, the modification time
> of the `directory` don't update now.
> So we should update the modification time of `directory`, otherwise, MR
> Jobhistory and some other component which use the modification time of
> `directory` cannot work as expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
