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 36F5118190 for ; Mon, 19 Oct 2015 11:48:57 +0000 (UTC) Received: (qmail 56899 invoked by uid 500); 19 Oct 2015 11:48:57 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 56851 invoked by uid 500); 19 Oct 2015 11:48:57 -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 56841 invoked by uid 99); 19 Oct 2015 11:48:57 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Oct 2015 11:48:57 +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 A7EF9C288C for ; Mon, 19 Oct 2015 11:48:56 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.174 X-Spam-Level: ** X-Spam-Status: No, score=2.174 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 4xHcgzHBzFXw for ; Mon, 19 Oct 2015 11:48:47 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTP id 07CA62545D for ; Mon, 19 Oct 2015 11:48:47 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 4E60717F1678 for ; Mon, 19 Oct 2015 04:40:01 -0700 (PDT) Date: Mon, 19 Oct 2015 04:40:55 -0700 (PDT) From: edwardk To: user@ignite.apache.org Message-ID: <1445254855436-1647.post@n6.nabble.com> Subject: Bulk load data at startup MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have a requirement to bulk load a lot of Master data which would be common to entire system. Since the Data store returns a huge number of rows, I feel the system might hang if we try to load all of them to memory. I am assuming it is possible , but not sure , if is is possible to load the data to a cluster of ignite nodes while fetching from database , in such a way , we do not utilize all available memory in the node on which the load is happening and at the same time distribute it across the nodes. What I mean is say if we have a data of size 500 MB to be loaded, can we distribute it across 5 nodes of 100 MB each during fetch time from database. Also, what would be the cache mode for this scenario. I feel replicated would not be better.But, not sure if partitioned mode is also better here, as in partitioned mode only one node has the data and backups of that data is in other nodes. So, am not sure what caching mode to use for this. Can someone help me on that approach to follow using apache ignite for this scenario. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Bulk-load-data-at-startup-tp1647.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.