[
https://issues.apache.org/jira/browse/HDFS-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036567#comment-18036567
]
ASF GitHub Bot commented on HDFS-16650:
---------------------------------------
github-actions[bot] commented on PR #4528:
URL: https://github.com/apache/hadoop/pull/4528#issuecomment-3507233735
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> Optimize the cost of obtaining timestamps in Centralized cache management
> -------------------------------------------------------------------------
>
> Key: HDFS-16650
> URL: https://issues.apache.org/jira/browse/HDFS-16650
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: caching
> Affects Versions: 2.9.2
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Getting timestamps in Centralized cache management is done in the following
> ways:
> {code:java}
> long now = new Date().getTime();
> {code}
> This approach doesn't seem to be optimal since we only use it once here.
> It might be better to use the tool Time to get the timestamp. E.g:
> {code:java}
> long now = Time.now();
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
