From oak-issues-return-29463-apmail-jackrabbit-oak-issues-archive=jackrabbit.apache.org@jackrabbit.apache.org Mon Feb 1 11:04:43 2016 Return-Path: X-Original-To: apmail-jackrabbit-oak-issues-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-oak-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2D4C318AEA for ; Mon, 1 Feb 2016 11:04:43 +0000 (UTC) Received: (qmail 13443 invoked by uid 500); 1 Feb 2016 11:04:40 -0000 Delivered-To: apmail-jackrabbit-oak-issues-archive@jackrabbit.apache.org Received: (qmail 13408 invoked by uid 500); 1 Feb 2016 11:04:40 -0000 Mailing-List: contact oak-issues-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oak-dev@jackrabbit.apache.org Delivered-To: mailing list oak-issues@jackrabbit.apache.org Received: (qmail 13395 invoked by uid 99); 1 Feb 2016 11:04:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Feb 2016 11:04:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D10892C1F57 for ; Mon, 1 Feb 2016 11:04:39 +0000 (UTC) Date: Mon, 1 Feb 2016 11:04:39 +0000 (UTC) From: "Julian Reschke (JIRA)" To: oak-issues@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OAK-3961) Cold Standby revisit timeout setup MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OAK-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126117#comment-15126117 ] Julian Reschke commented on OAK-3961: ------------------------------------- Test failures over here: {noformat} Failed tests: testFailoverCorrectList(org.apache.jackrabbit.oak.plugins.segment.standby.FailoverIPRangeTest): expected:<{ root = { ... } }> but was:<{ root : { } }> testFailoverCorrectListIPv6UseIPv6(org.apache.jackrabbit.oak.plugins.segment.standby.FailoverIPRangeTest): expected:<{ root = { ... } }> but was:<{ root : { } }> testFailoverCorrectListUseIPv6(org.apache.jackrabbit.oak.plugins.segment.standby.FailoverIPRangeTest): expected:<{ root = { ... } }> but was:<{ root : { } }> testFailoverCorrectListIPv6(org.apache.jackrabbit.oak.plugins.segment.standby.FailoverIPRangeTest): expected:<{ root = { ... } }> but was:<{ root : { } }> {noformat} > 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 > > 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)