[
https://issues.apache.org/jira/browse/HADOOP-16266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827074#comment-16827074
]
Erik Krogen commented on HADOOP-16266:
--------------------------------------
Hi [~ste...@apache.org], thanks for sharing your thoughts. I see that blog post
is from 2015. Other explanations I have found indicate that what you describe
used to be a very significant problem, but that in modern JDKs (7+), the JVM
guarantees that System.nanoTime works as you would expect even in the face of
multi-cored systems. This guarantee was originally plagued by bugs, but all
known outstanding issues have been fixed, so IIUC from my reading, there should
be no more issues in using it as such. Do you believe that all of your concerns
from 2015 are still relevant in today's world?
> Add more fine-grained processing time metrics to the RPC layer
> --------------------------------------------------------------
>
> Key: HADOOP-16266
> URL: https://issues.apache.org/jira/browse/HADOOP-16266
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Reporter: Christopher Gregorian
> Assignee: Christopher Gregorian
> Priority: Minor
> Labels: rpc
> Attachments: HADOOP-16266.001.patch, HADOOP-16266.002.patch,
> HADOOP-16266.003.patch, HADOOP-16266.004.patch, HADOOP-16266.005.patch
>
>
> Splitting off of HDFS-14403 to track the first part: introduces more
> fine-grained measuring of how a call's processing time is split up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
