You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2018/02/22 03:25:00 UTC
[jira] [Assigned] (KARAF-5633) Cellar: cleanup Hazelcast maps when
a group is deleted
[ https://issues.apache.org/jira/browse/KARAF-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-5633:
-------------------------------------------
Assignee: Jean-Baptiste Onofré
> Cellar: cleanup Hazelcast maps when a group is deleted
> ------------------------------------------------------
>
> Key: KARAF-5633
> URL: https://issues.apache.org/jira/browse/KARAF-5633
> Project: Karaf
> Issue Type: Bug
> Components: cellar-hazelcast
> Affects Versions: cellar-4.0.4, cellar-4.1.1
> Reporter: Sergiy Shyrkov
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
>
> When a Cellar group is deleted, the corresponding Hazelcast maps remain there (org.apache.karaf.cellar.bundle.map.<group-name>, org.apache.karaf.cellar.repositories.<group-name>, org.apache.karaf.cellar.features.<group-name>, etc.).
> In effect, when the group is created again, those maps are taken with "stale" data.
>
> My use case:
> 1) Create a new group "temp"
> 2) Move one node (node1) to that group "temp" (the node is removed from "default" group)
> 3) Deploy some bundles on group "temp"
> 4) Remove node1 from group "temp" and bring it back to group "default"
> 5) Delete group "temp" (at this point the Hazelcast map date remains for that group)
> 6) When I create again the group "temp" and join node1, the cluster state is pulled from the old data and applied to my node1.
> Thank you!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)