[
https://issues.apache.org/jira/browse/SLING-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved SLING-2967.
--------------------------------
Resolution: Fixed
fixed by resetting the created time of a topology announcement before
persisting it.
persisting a topology announcement happens on both side of a topology
connector. the 'created' field contained the origin's local machine time. this
caused issues when the clocks are not in sync. the fix is to redefine 'created'
as 'receive-time', thus always working with local times only
> Make topology connectors independent from machine clocks differences
> --------------------------------------------------------------------
>
> Key: SLING-2967
> URL: https://issues.apache.org/jira/browse/SLING-2967
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Discovery Impl 1.0.0
> Reporter: Stefan Egli
> Assignee: Stefan Egli
>
> In a setup where two machines use discovery.impl to connect the topology
> between each other - and the two machines's clock have a considerable
> difference, say 1min - the discovery.impl rejects the incoming announcement,
> treating it as 'expired'.
> While in theory it is reasonable to assume that server clocks in data centers
> run fairly in-sync, it is still safer to avoid any dependency on the accuracy
> of clocks.
> The topology connector should not be dependent on those clocks and not pass
> times as part of the announcement-json - but rather stamp incoming
> announcements with local clocks.
--
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
