Return-Path: X-Original-To: apmail-cayenne-user-archive@www.apache.org Delivered-To: apmail-cayenne-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7E5FE18146 for ; Fri, 11 Dec 2015 18:54:43 +0000 (UTC) Received: (qmail 54215 invoked by uid 500); 11 Dec 2015 18:54:43 -0000 Delivered-To: apmail-cayenne-user-archive@cayenne.apache.org Received: (qmail 54169 invoked by uid 500); 11 Dec 2015 18:54:43 -0000 Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cayenne.apache.org Delivered-To: mailing list user@cayenne.apache.org Delivered-To: moderator for user@cayenne.apache.org Received: (qmail 40104 invoked by uid 99); 11 Dec 2015 18:52:11 -0000 X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.898 X-Spam-Level: ** X-Spam-Status: No, score=2.898 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=levelsbeyond.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=levelsbeyond.com; s=google; h=mime-version:from:date:message-id:subject:to:content-type; bh=kCwAy2IN++lV3/mobe8oZ3ZlUEU3hPeTFm6YBSZTHSc=; b=Kx9lbIwhOdb2o4OklhTmG0LvexGiVW7qE3uUbi83MsuIUTyQ15l5nFuCXM9TyS5zNJ 2OLN64NmSgyrFHaBDLvWqfQzC5j5oCq2SGEf8cCQxH/DbKaajTDKOPBiXTtUTAtZb3b5 TXSHKbpkxywG+kc93IAFczuCc3ulpv/ibtjwE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=kCwAy2IN++lV3/mobe8oZ3ZlUEU3hPeTFm6YBSZTHSc=; b=GSk3UMQvZhCKDmsP3zQpiPXMaMgpsHhFJyYwLv5EdUL+DeAKb+8OdJa6uLpEA6xPJH DL5iINv/+mLBIRlp2MadHDLo2iz+ZrlZkP/QlemwBnUpkeKHGoaQVfCSPYIcGw1Vw0+w VIzNh6zVILOpiQNrVYIAoHuCu2h1A3k/Z3v92IJzALT+viBfgb3ntbyivwZkzinvJpjM 61tqoDaasYlyBdpezaAc7pEFXl1ID9tX2igJhQnWUlMQlkdDO8QtkV9r2Csa+tGYr03L 2AXcSyvoqBA018DAENy5yu8cIpITNfAUm/P2OBRM1uK/J/YdxHONXMvyKrexCMcGE6Wb HyVg== X-Gm-Message-State: ALoCoQlMYysEOPsrF+pNDQua1eci8+brT7mn6AkLWHQTJ07bZZpMp2zPbd/r3yhrj++Lfmd9CMRu2QFFcq3bQ9mqmviD4xBw7A== X-Received: by 10.107.133.16 with SMTP id h16mr16862566iod.79.1449859927716; Fri, 11 Dec 2015 10:52:07 -0800 (PST) MIME-Version: 1.0 From: Eric Cobb Date: Fri, 11 Dec 2015 18:51:57 +0000 Message-ID: Subject: Configuring the Cache in a multi-node environment. (cayenne 3.0) To: user@cayenne.apache.org Content-Type: multipart/alternative; boundary=001a113f9a3af749590526a3d1e0 --001a113f9a3af749590526a3d1e0 Content-Type: text/plain; charset=UTF-8 Hello All! I am looking for resources on how to best configure cayenne when running in a cluster, or multiple JVMs using the same domain. I've been reading the documentation and I see this: "there are ways to notify other stacks about the object changes. This can be set up in the Modeler. However full synchronization of every change often results in excessive network traffic and CPU consumption, and is usually avoided in favor of the query cache approach described elsewhere in this chapter." That links to the Query-Result-Caching page. It is my understanding that object caching is used when an associated object is retrieved via a getter or when an object is retrieved by its id. Is this quote telling me that if I configure query caching, object caching won't be used? Or that I need to avoid doing that would hit the object cache in my application code? Should I disable the object cache completely (if that's even possible)? If I don't set up cayenne to notify other stacks of changes to the object cache, don't I run the risk of stale data? I appreciate any and all tips on the best way to run cayenne across multiple nodes, or if you have some resources to point me toward, that would be very helpful as well. Thanks in advance for your time! --001a113f9a3af749590526a3d1e0--