From issues-return-30021-archive-asf-public=cust-asf.ponee.io@geode.apache.org Wed Jan 31 22:38:05 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 45E5A180662 for ; Wed, 31 Jan 2018 22:38:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 357B3160C42; Wed, 31 Jan 2018 21:38:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7DB03160C2C for ; Wed, 31 Jan 2018 22:38:04 +0100 (CET) Received: (qmail 74931 invoked by uid 500); 31 Jan 2018 21:38:03 -0000 Mailing-List: contact issues-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list issues@geode.apache.org Received: (qmail 74922 invoked by uid 99); 31 Jan 2018 21:38:03 -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, 31 Jan 2018 21:38:03 +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 46B191A5ACB for ; Wed, 31 Jan 2018 21:38:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -101.511 X-Spam-Level: X-Spam-Status: No, score=-101.511 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, 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-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 4y25q3gw1Hfp for ; Wed, 31 Jan 2018 21:38:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 23FA65F1ED for ; Wed, 31 Jan 2018 21:38:02 +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 2CED4E0220 for ; Wed, 31 Jan 2018 21:38:01 +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 9D5B724106 for ; Wed, 31 Jan 2018 21:38:00 +0000 (UTC) Date: Wed, 31 Jan 2018 21:38:00 +0000 (UTC) From: "Alexander Murmann (JIRA)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (GEODE-4308) Should be able to create two caches in the same JVM MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/GEODE-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347655#comment-16347655 ] Alexander Murmann commented on GEODE-4308: ------------------------------------------ Many of the issues we will run into making it possible to run multiple caches in one JVM are due to questionable design decisions. There is no doubt in my mind that the Geode codebase will be in better state once there is nothing left that prohibits us from running more than one cache in a JVM. So this goal might be a great guiding start for future refactors. The testing benefit of multiple caches in the same JVM also has come up in prior refactoring discussions. I agree with Anil though that exposing multiple caches in one JVM to the user is a discussion that should be done with care. > Should be able to create two caches in the same JVM > --------------------------------------------------- > > Key: GEODE-4308 > URL: https://issues.apache.org/jira/browse/GEODE-4308 > Project: Geode > Issue Type: Sub-task > Components: messaging > Reporter: Dan Smith > Assignee: Dan Smith > Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Users should be able to create two or more caches in the same JVM. > Currently this is impossible because we have a static instance variable that only allows a single cache. > We should add a feature flag to let us start getting multiple caches to work if that feature flag is enabled. For this task we will add the feature flag and enable creating multiple caches in the same JVM. Not all cache features will work yet, just the CacheFactory.create(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)