Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D5BFA196C4 for ; Thu, 21 Apr 2016 18:45:29 +0000 (UTC) Received: (qmail 36549 invoked by uid 500); 21 Apr 2016 18:45:29 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 36504 invoked by uid 500); 21 Apr 2016 18:45:29 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 36492 invoked by uid 99); 21 Apr 2016 18:45:29 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Apr 2016 18:45:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 479CFC1A4E for ; Thu, 21 Apr 2016 18:45:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id kIcaBRbFSXg5 for ; Thu, 21 Apr 2016 18:45:27 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTP id B76325FBB2 for ; Thu, 21 Apr 2016 18:45:26 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id C071025D6CE5 for ; Thu, 21 Apr 2016 11:31:46 -0700 (PDT) Date: Thu, 21 Apr 2016 11:31:20 -0700 (PDT) From: vkulichenko To: user@ignite.apache.org Message-ID: <1461263480427-4421.post@n6.nabble.com> In-Reply-To: <1461232807799-4410.post@n6.nabble.com> References: <1461232807799-4410.post@n6.nabble.com> Subject: Re: Ignite Transactions for Out Process Grids MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Can you please properly subscribe to the mailing list so that the community can receive email notifications? Here is the instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 amit2103 wrote > Can Ignite transactions work if Grids are out process? > > Why is this document written in Ignite Spring Transaction Manager :- > >Start an Ignite node with proper configuration in embedded mode? > > Can Ignite Transactions work only when Grid is in embedded mode? You need an embedded node to access the cluster and use Ignite API and this node can be either client or server [1]. You can also have as many standalone nodes as you want. They will store the data and the transaction will be distributed across all required nodes. [1] https://apacheignite.readme.io/docs/clients-vs-servers -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Transactions-for-Out-Process-Grids-tp4410p4421.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.