[
https://issues.apache.org/jira/browse/HDFS-13901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938253#comment-16938253
]
Jinglun commented on HDFS-13901:
--------------------------------
Thanks [~jojochuang] for your nice comments ! I delete the old comment and
change to DFSTestUtil.createFile, it's cleaner now.
{quote}Can you use something else other than sleep 1ms? Like CountDownLatch or
semaphore? Using sleep 1ms to control order of threads is almost always going
to create flaky tests.
{quote}
Very thoughtful ! Using sleep 1ms is a bad idea, I change to Semaphore.
Upload v05 and pending jenkins.
> INode access time is ignored because of race between open and rename
> --------------------------------------------------------------------
>
> Key: HDFS-13901
> URL: https://issues.apache.org/jira/browse/HDFS-13901
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Jinglun
> Assignee: Jinglun
> Priority: Major
> Attachments: HDFS-13901.000.patch, HDFS-13901.001.patch,
> HDFS-13901.002.patch, HDFS-13901.003.patch, HDFS-13901.004.patch,
> HDFS-13901.005.patch
>
>
> That's because in getBlockLocations there is a gap between readUnlock and
> re-fetch write lock (to update access time). If a rename operation occurs in
> the gap, the update of access time will be ignored. We can calculate new path
> from the inode and use the new path to update access time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
