Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AF1CA18D2E for ; Mon, 29 Jun 2015 17:51:41 +0000 (UTC) Received: (qmail 19897 invoked by uid 500); 29 Jun 2015 17:51:41 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 19860 invoked by uid 500); 29 Jun 2015 17:51:41 -0000 Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.incubator.apache.org Delivered-To: mailing list dev@ignite.incubator.apache.org Received: (qmail 19848 invoked by uid 99); 29 Jun 2015 17:51:41 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jun 2015 17:51:41 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id C4777C09C6 for ; Mon, 29 Jun 2015 17:51:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.979 X-Spam-Level: ** X-Spam-Status: No, score=2.979 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ZluPmms1d1yc for ; Mon, 29 Jun 2015 17:51:39 +0000 (UTC) Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 6410B2122D for ; Mon, 29 Jun 2015 17:51:39 +0000 (UTC) Received: by lagh6 with SMTP id h6so63003984lag.2 for ; Mon, 29 Jun 2015 10:51:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=SCoyjN11Dz2vrcOj3wStN7H99B4pTysVh9iJLBG60SA=; b=T7rKXu0r7fbdZkTUCU2gMWXbyqgDRQPOplPC9g2eKlbh3GdDHxjhd1PhJgFaMrUwRl pmlcMqDo3LjRx35/v2gKxRtOaP4VJJ8AtXg4CHHrJwd0RTDfwEdx2+tEput6lvuYdlYf 1mCBQWV60JzyLzc599LCnAYmXx2QiwlGt13H9UfoyfxJfCppRmAH+jsE46DFVEYJp/QJ v/e5EHtXk43PomJAbkgEUwC3Xw9uLbA0Lbzp6f9RRzFXHkDevqLRuyrBdfWEujRc/aB8 1V1i/85lZYTZS1T5CYCzEIKqRD3j47otL3lYTNFoivIpbMXuOE0VyrQDiDN+TBs+FhOl YOvw== X-Gm-Message-State: ALoCoQkLOjkB4JjDtJ0aJcyICecuPE5r3RFkhJYbhxiWas/Eu+36DAvgTKv+NhQ3+tNXA0Bl9VoJ MIME-Version: 1.0 X-Received: by 10.152.164.193 with SMTP id ys1mr15355358lab.65.1435600297892; Mon, 29 Jun 2015 10:51:37 -0700 (PDT) Received: by 10.114.242.4 with HTTP; Mon, 29 Jun 2015 10:51:37 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Jun 2015 20:51:37 +0300 Message-ID: Subject: Re: destroying cache when IgniteCache.close() From: Anton Vinogradov To: dev@ignite.incubator.apache.org Content-Type: multipart/alternative; boundary=001a1133c258cbb8a30519abbdfc --001a1133c258cbb8a30519abbdfc Content-Type: text/plain; charset=UTF-8 Hello, Task https://issues.apache.org/jira/browse/IGNITE-929 was not merged to latest release due risk of unexpected problems. TC was overloaded and I had no chance to test this feature appropriately. Going to prepare it for final review next days and merge before next release. On Mon, Jun 29, 2015 at 8:07 PM, Dmitriy Setrakyan wrote: > Igniters, > > I thought that we stopped deleting the whole cache whenever > IgniteCache.close() method is called. However, I just tested it on the GG > community edition 1.1.4 (which is the same as the about to be released 1.2) > and I still see the whole cache being destroyed. > > Can someone comment? > > D. > --001a1133c258cbb8a30519abbdfc--