[
https://issues.apache.org/jira/browse/TS-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722055#comment-13722055
]
Leif Hedstrom commented on TS-2079:
-----------------------------------
Doing this eliminates a bunch of code where we calculate this drifted clock,
and well as having to assign intermediary values where we could otherwise just
use fixed times (such as negative cache liftime).
> Replace ink_cluster_time() with just "localtime"
> ------------------------------------------------
>
> Key: TS-2079
> URL: https://issues.apache.org/jira/browse/TS-2079
> Project: Traffic Server
> Issue Type: Improvement
> Components: Clustering, Core
> Reporter: Leif Hedstrom
> Fix For: 3.5.0
>
>
> I think this shared "adjustment" of a time concept across a cluster is
> generally pointless these days. What it does it to take a negative approach,
> and use the largest skew as an offset on each box. This is to e.g. allow for
> cluster cache object to live at a duration based on the fastest clock.
> It's possible this was a useful feature in the past, but honestly, with NTP
> being ubiquitous, I think we should just assume that the clocks are within
> reasonable skew inside the cluster.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
