You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:36:08 UTC
[jira] [Updated] (HDDS-3545) MR Jobhistory cannot work well with
o3fs hadoop compatible file system
[ https://issues.apache.org/jira/browse/HDDS-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose updated HDDS-3545:
-----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org