You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2014/03/11 22:06:45 UTC
[jira] [Resolved] (TS-2079) Replace ink_cluster_time() with just
"localtime"
[ https://issues.apache.org/jira/browse/TS-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom resolved TS-2079.
-------------------------------
Resolution: Duplicate
Fix Version/s: (was: 5.0.0)
> 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
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)