You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Ioannis Canellos (Created) (JIRA)" <ji...@apache.org> on 2011/12/03 19:34:40 UTC
[jira] [Created] (KARAF-1082) Cellar group configuration is not
properly distributed to the cluster
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.1, cellar-2.2.2
Reporter: Ioannis Canellos
Assignee: Ioannis Canellos
Fix For: cellar-3.0.0, cellar-2.2.3
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-1082) Cellar group configuration is not
properly distributed to the cluster
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-1082:
----------------------------------------
Fix Version/s: (was: cellar-2.2.4)
cellar-2.2.5
> 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: Ioannis Canellos
> Fix For: cellar-3.0.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KARAF-1082) Cellar group configuration is not
properly distributed to the cluster
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-1082:
-------------------------------------------
Assignee: Jean-Baptiste Onofré (was: Ioannis Canellos)
> 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.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-1082) Cellar group configuration is not
properly distributed to the cluster
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-1082:
----------------------------------------
Fix Version/s: (was: cellar-2.2.3)
cellar-2.2.4
> 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: Ioannis Canellos
> Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-1082) Cellar group configuration is not
properly distributed to the cluster
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-1082:
----------------------------------------
Fix Version/s: (was: cellar-2.2.5)
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.6
>
>
> 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
[jira] [Updated] (KARAF-1082) Cellar group configuration is not
properly distributed to the cluster
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-1082:
----------------------------------------
Fix Version/s: cellar-2.3.0
> 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.6
>
>
> 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