karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (KARAF-1082) Cellar group configuration is not properly distributed to the cluster
Date Mon, 28 Jan 2013 18:23:13 GMT

     [ https://issues.apache.org/jira/browse/KARAF-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jean-Baptiste Onofré resolved KARAF-1082.

       Resolution: Fixed
    Fix Version/s:     (was: cellar-2.2.6)
> Cellar group configuration is not properly distributed to the cluster
> ---------------------------------------------------------------------
>                 Key: KARAF-1082
>                 URL: https://issues.apache.org/jira/browse/KARAF-1082
>             Project: Karaf
>          Issue Type: Improvement
>          Components: cellar-hazelcast
>    Affects Versions: cellar-2.2.2, cellar-2.2.1
>            Reporter: Ioannis Canellos
>            Assignee: Jean-Baptiste Onofré
>             Fix For: cellar-3.0.0, cellar-2.3.0, cellar-2.2.5
> Currently when a node is assigned a new group, the node will create the group configuration
inherited from the default group and store the configuration locally.
> If the group already exists, then it will wait for a configuration sync till it gets
the group config. This can have unexpected results since its possible to operate for a while
with out of sync configuration.
> The group configuration needs to be sync, to ALL cluster nodes. So it needs to be stored
to Hazelcast and synchronize with the config found in the configuration admin.
> A solution would be to have the group manager be a configuration listener and Hazelcast
item listener and implement the sync there.

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

View raw message