[jira] [Commented] (OAK-5446) leaseUpdateThread might be blocked by leaseUpdateCheck

[Gavin (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849705#comment-15849705
 ] 

Gavin commented on OAK-5446:


[~reschke] ok can you check if this ticket has its normal buttons back?

> leaseUpdateThread might be blocked by leaseUpdateCheck
> --
>
> Key: OAK-5446
> URL: https://issues.apache.org/jira/browse/OAK-5446
> Project: Jackrabbit Oak
>  Issue Type: Bug
>Affects Versions: 1.4, 1.5.14
>Reporter: Stefan Eissing
>Assignee: Julian Reschke
> Attachments: OAK-5446.diff, OAK-5446-jr.diff, OAK-5446.testcase, 
> OAK-5446.testcase.v3
>
>
> {color:red}
> moved over to OAK-5528 due to internal Jira issues, please do not delete this 
> ticket while the problem is being investigated
> {color}
> Fighting with cluster nodes losing their lease and shutting down oak-core in 
> a cloud environment. For reasons unknown at this point in time, the whole 
> process seems to skip about two minutes of real time.
> This is a situation from which oak currently does not recover. Code analysis 
> shows that {{ClusterNodeInfo}} is handed the 
> {{LeaseCheckDocumentStoreWrapper}} instance to use as store. This is fatal 
> since any action the {{renewLease()}} tries to do will first invoke the 
> {{performLeaseCheck()}}. The lease check will, when the {{FailureMargin}} is 
> reached, _stall the renewLease() thread_ for 5 retry attempts and then 
> declare the lease to be lost.
> The {{ClusterNodeInfo}} should instead be using the "real" {{DocumentStore}}, 
> not the wrapped one, IMO.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-5017) Standby test failures

[Gavin (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733105#comment-15733105
 ] 

Gavin commented on OAK-5017:


I added an Axis to use the 'label' expression. The 'Slaves' Axis used to work 
but stopped working a short time ago, I filed a Jenkins ticket with no response 
so far.

> Standby test failures
> -
>
> Key: OAK-5017
> URL: https://issues.apache.org/jira/browse/OAK-5017
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Francesco Mari
>  Labels: test-failure
> Fix For: 1.6, 1.5.16
>
>
> I've recently seen a couple of the standby tests fail. E.g. on Jenkins: 
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1245/
> {noformat}
> java.lang.AssertionError: expected: 
> org.apache.jackrabbit.oak.segment.SegmentNodeState<{ checkpoints = { ... }, 
> root = { ... } }> but was: 
> org.apache.jackrabbit.oak.segment.SegmentNodeState<{ checkpoints = { ... }, 
> root = { ... } }>
>   at 
> org.apache.jackrabbit.oak.segment.standby.StandbyTestIT.testSyncLoop(StandbyTestIT.java:122)
> {noformat}
> {noformat}
> java.lang.AssertionError: expected: 
> org.apache.jackrabbit.oak.segment.SegmentNodeState<{ checkpoints = { ... }, 
> root = { ... } }> but was: 
> org.apache.jackrabbit.oak.segment.SegmentNodeState<{ checkpoints = { ... }, 
> root = { ... } }>
>   at 
> org.apache.jackrabbit.oak.segment.standby.StandbyTestIT.testSyncLoop(StandbyTestIT.java:122)
> {noformat}
> {{org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT.testProxySkippedBytes}}:
> {noformat}
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { } 
> }>
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)