[
https://issues.apache.org/jira/browse/HDDS-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142212#comment-17142212
]
Arpit Agarwal edited comment on HDDS-3545 at 6/22/20, 3:54 PM:
---------------------------------------------------------------
HDDS-2939 should be done for 0.7.0 release.
How does Jobhistory handle this when working over S3A?
cc [~msingh] [~rakeshr].
was (Author: arpitagarwal):
HDDS-2939 should be done for 0.7.0 release.
How does Jobhistory handle this when working over S3A?
> MR Jobhistory cannot work well with o3fs hadoop compatible file system
> ----------------------------------------------------------------------
>
> Key: HDDS-3545
> URL: https://issues.apache.org/jira/browse/HDDS-3545
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Filesystem
> Reporter: maobaolong
> Priority: Major
> Labels: TriagePending
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
