From issues-return-26922-apmail-karaf-issues-archive=karaf.apache.org@karaf.apache.org Wed Nov 18 16:53:11 2015 Return-Path: X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org Delivered-To: apmail-karaf-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 6872918D0E for ; Wed, 18 Nov 2015 16:53:11 +0000 (UTC) Received: (qmail 62419 invoked by uid 500); 18 Nov 2015 16:53:11 -0000 Delivered-To: apmail-karaf-issues-archive@karaf.apache.org Received: (qmail 62372 invoked by uid 500); 18 Nov 2015 16:53:11 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 62104 invoked by uid 99); 18 Nov 2015 16:53:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Nov 2015 16:53:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 08B1A2C1F6A for ; Wed, 18 Nov 2015 16:53:11 +0000 (UTC) Date: Wed, 18 Nov 2015 16:53:11 +0000 (UTC) From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Work started] (KARAF-4115) Hard coded timeout values for Cellar shell commands MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KARAF-4115?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4115 started by Jean-Baptiste Onofr=C3=A9. --------------------------------------------------- > Hard coded timeout values for Cellar shell commands > --------------------------------------------------- > > Key: KARAF-4115 > URL: https://issues.apache.org/jira/browse/KARAF-4115 > Project: Karaf > Issue Type: Bug > Components: cellar-core, cellar-shell > Affects Versions: cellar-4.0.0, cellar-3.0.3 > Reporter: Matej Ferencak > Assignee: Jean-Baptiste Onofr=C3=A9 > Fix For: cellar-3.0.4, cellar-4.0.1 > > > In Cellar, all commands seem to be set to timeout after 10s. > This is causing us a lot of problems in situations when there are multipl= e Karaf Instances deployed on multiple nodes (we usually deploy a total of = 12-14 overall instances on 4 different VMs), when Hazelcast tends to be rea= lly slow due to network traffic during cluster synchronization. > In such a setup, running *cluster:group-set* can be very slow, and 50% of= the time it times out. Once this happens, the node is unuseable, i.e. it e= nters an undefined state where it can not easily join or quit a cluster gro= up any more. > There are a couple of places in code where this can be found: > org.apache.karaf.cellar.core.command.Command : timeout =3D 10000 > org.apache.karaf.cellar.core.event.EventDispatchTask : timeout =3D 10000 > (referencing Karaf 4.0.3 master) > I can't find it right now, but a very similar thing seems to be implement= ed in Karaf Shell, where I think I saw the value being bumped from 10s to a= higher value of 30s at some point in history (but still hard coded). > Currently, we are working around this by re-implementing the *cluster:gro= up-set* by invoking Karaf Cellar services directly (ClusterManager & GroupM= anager). Since we implemented this, we don't have problems with cluster set= up any more. > It would be great if this value could be somehow made configurable, or as= the last resort, increased. -- This message was sent by Atlassian JIRA (v6.3.4#6332)