[
https://issues.apache.org/jira/browse/BOOKKEEPER-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422015#comment-13422015
]
Uma Maheswara Rao G commented on BOOKKEEPER-330:
------------------------------------------------
Yes, I have seen that backward times in multicore machines in both the cases
(CurrentTimeMillis and nanoTime). Also added the same comment in BK-327 as well.
I think we should not completely depend on this system times for sensitive
opretaions like array access ..etc. This patch adds the check for negative on
latency because there will be chance for backward times in all the cases.
counter based time calculation would be better than currentTimeMillis. But I am
not sure the change you are proposing here will be really required.
You mean, we will calculate all the time diffs with currentMillis, nanoTime and
average out the elapsed time? That may messup the things I feel. Because always
there may inaccuracy in times due to the mismatches in currentMillis and
nanoTime right. Please correct me, If I understand your point wrongly.
> System.currentTimeMillis usage in Hedwig
> ----------------------------------------
>
> Key: BOOKKEEPER-330
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-330
> Project: Bookkeeper
> Issue Type: Bug
> Components: hedwig-server
> Affects Versions: 4.0.0, 4.1.0
> Reporter: Sijie Guo
> Assignee: Uma Maheswara Rao G
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-330.patch
>
>
> Need same changes in hedwig server as what did in bookkeeper as
> BOOKKEEPER-327.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
