From issues-return-38861-archive-asf-public=cust-asf.ponee.io@karaf.apache.org Wed Feb 21 14:09:08 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8AE1118077A for ; Wed, 21 Feb 2018 14:09:06 +0100 (CET) Received: (qmail 65140 invoked by uid 500); 21 Feb 2018 13:09:05 -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 65073 invoked by uid 99); 21 Feb 2018 13:09:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Feb 2018 13:09:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0F19B1A06EA for ; Wed, 21 Feb 2018 13:09:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -102.311 X-Spam-Level: X-Spam-Status: No, score=-102.311 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 8UnoZnYQaNhn for ; Wed, 21 Feb 2018 13:09:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 9A5355F58D for ; Wed, 21 Feb 2018 13:09:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C9942E0254 for ; Wed, 21 Feb 2018 13:09:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2E8A521090 for ; Wed, 21 Feb 2018 13:09:00 +0000 (UTC) Date: Wed, 21 Feb 2018 13:09:00 +0000 (UTC) From: "Sergiy Shyrkov (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KARAF-5633) Cellar: cleanup Hazelcast maps when a group is deleted MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sergiy Shyrkov created KARAF-5633: ------------------------------------- Summary: Cellar: cleanup Hazelcast maps when a group is delete= d Key: KARAF-5633 URL: https://issues.apache.org/jira/browse/KARAF-5633 Project: Karaf Issue Type: Bug Components: cellar-hazelcast Affects Versions: cellar-4.1.1, cellar-4.0.4 Reporter: Sergiy Shyrkov When a Cellar=C2=A0group is deleted, the corresponding Hazelcast maps remai= n there (org.apache.karaf.cellar.bundle.map., org.apache.karaf.= cellar.repositories.,=C2=A0 org.apache.karaf.cellar.features., etc.). In effect, when the group is created again, those maps are taken with "stal= e" data. =C2=A0 My use case: 1) Create a new group "temp" 2) Move one node (node1) to that group "temp" (the node is removed from "de= fault" group) 3)=C2=A0Deploy 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 th= at group) 6) When I create again the group "temp" and join node1, the cluster state i= s pulled from the old data=C2=A0and applied to my node1. Thank you! -- This message was sent by Atlassian JIRA (v7.6.3#76005)