[
https://issues.apache.org/jira/browse/SLING-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved SLING-5260.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: Discovery Base 1.0.2)
(was: Discovery Impl 1.2.2)
Discovery Base 1.0.4
test adjusted in 1712546
> AbstractClusterTest.testConnectorSwitching4139 test parameters too tight
> ------------------------------------------------------------------------
>
> Key: SLING-5260
> URL: https://issues.apache.org/jira/browse/SLING-5260
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Discovery Base 1.0.2
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Fix For: Discovery Base 1.0.4
>
>
> AbstractClusterTest.testConnectorSwitching4139 has a part where it has 5
> instances, then crashes 1 and wants to make sure that its crash is properly
> propagated through the topology. The problem is, that instance has a timeout
> of 10sec. And the loop does at least 20x500ms and ensures that the crashed
> instance is properly noticed *within its cluster by its peer instance*
> (only). That doesn't mean though, that it also propagated to the others via
> connectors - as that would just yet happen with the next heartbeat.
> So in short: those 20x500ms looping are too close to the 10sec timeout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
