[ https://issues.apache.org/jira/browse/OAK-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126882#comment-15126882 ]
Alex Parvulescu commented on OAK-3961: -------------------------------------- ... and it's gone (OAK-3967, disabled the test) > Cold Standby revisit timeout setup > ---------------------------------- > > Key: OAK-3961 > URL: https://issues.apache.org/jira/browse/OAK-3961 > Project: Jackrabbit Oak > Issue Type: Bug > Components: tarmk-standby > Reporter: Alex Parvulescu > Assignee: Alex Parvulescu > Labels: candidate_oak_1_2 > Fix For: 1.3.15 > > > The timeout settings are too large and inefficient, making all the tests very > slow. On top of this the current timeout if being enforced in 2 places, which > turns out it doesn't play too well with the sync mechanism: > * one is via the _ReadTimeoutHandler_ in the _StandbyClient_ > * second is in the _SegmentLoaderHandler_ > as it turns out the first one is a global kill switch, and it will fail any > transaction larger than the set value (_all_ of the sync cycle), which is not > what I meant to do with it, so I'll remove it and only leave the second one, > which is a timeout per request (segment or binary). -- This message was sent by Atlassian JIRA (v6.3.4#6332)