[
https://issues.apache.org/jira/browse/HDFS-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234900#comment-14234900
]
Charles Lamb commented on HDFS-7463:
------------------------------------
Hi [~wheat9],
The changes to now() seem fine in .002.
bq. My concern is that the lists are neither complete nor consistent in most
cases.
I feel your pain. I might suggest that this is an issue for a different Jira
perhaps? It feels like something of a policy change that should be addressed in
a more all-or-nothing scale rather than a one-off targeted approach.
Charles
> Simplify FSNamesystem#getBlockLocationsUpdateTimes
> --------------------------------------------------
>
> Key: HDFS-7463
> URL: https://issues.apache.org/jira/browse/HDFS-7463
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Attachments: HDFS-7463.000.patch, HDFS-7463.001.patch,
> HDFS-7463.002.patch
>
>
> Currently {{FSNamesystem#getBlockLocationsUpdateTimes}} holds the read lock
> to access the blocks. It releases the read lock and then acquires the write
> lock when it needs to update the access time of the {{INode}}.
> This jira proposes to move the responsibility of the latter steps to the
> caller to simplify the code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
