Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Mon, 28 Jan 2013 18:07:13 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12554892.1336736783030.201759.1359396433148@arcas>
In-Reply-To: <JIRA.12554892.1336736783030@arcas>
References: <JIRA.12554892.1336736783030@arcas>
Subject: [jira] [Commented] (KARAF-1467) groups configuration is not
 syncronized normally.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-1467?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1356=
4457#comment-13564457 ]=20

Jean-Baptiste Onofr=C3=A9 commented on KARAF-1467:
---------------------------------------------

In Cellar 2.2.5, we introduced the groups list in etc/org.apache.karaf.cell=
ar.groups.cfg. So, only group members have the group configuration (includi=
ng blacklist, whitelist, etc). So I don't think that it's an used anymore t=
hanks to the groups list properties.
               =20
> groups configuration is not syncronized normally.
> -------------------------------------------------
>
>                 Key: KARAF-1467
>                 URL: https://issues.apache.org/jira/browse/KARAF-1467
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-config
>    Affects Versions: cellar-2.2.3
>            Reporter: Alexandr Palto
>            Assignee: Jean-Baptiste Onofr=C3=A9
>             Fix For: cellar-3.0.0, cellar-2.2.5
>
>
> 1) Start three karaf instances (node1, node2, node3).
> 2) Install cellar on every of them
> 3) Create group "testgroup" on node1
> 4) Join node3 into testgroup (cluster:group-join testgroup node3)
> 5) Check org.apache.karaf.cellar.groups.cfg on every node: not all config=
s contain properties related to new group (sometimes only one contains, som=
etimes two. In my test only node2 contained this config just after creation=
, after restart also node3 takes this config.)
> 6) Shutdown cluster
> 7) Startup cluster: even after that not all nodes contains all properties=
 related to group configs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira