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 4AA5017CD3 for ; Mon, 25 May 2015 18:06:19 +0000 (UTC) Received: (qmail 47561 invoked by uid 500); 25 May 2015 18:06:03 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 47519 invoked by uid 500); 25 May 2015 18:06:03 -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 47506 invoked by uid 99); 25 May 2015 18:06:03 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 May 2015 18:06: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 ACF7D1A33F1 for ; Mon, 25 May 2015 18:06:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.98 X-Spam-Level: ** X-Spam-Status: No, score=2.98 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, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 4L8QGzKT__Il for ; Mon, 25 May 2015 18:05:56 +0000 (UTC) Received: from mail-qk0-f181.google.com (mail-qk0-f181.google.com [209.85.220.181]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 92E2F20510 for ; Mon, 25 May 2015 18:05:56 +0000 (UTC) Received: by qkdn188 with SMTP id n188so70028787qkd.2 for ; Mon, 25 May 2015 11:04:25 -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=jkNBQ3F+wMPiXkmokEMpzFpXBjiQfMVMfjSOPTYJyaQ=; b=Chsz4S1dPxco2pPwwcrUcOcubdG/TwuIREbLatT5YRfCtiIiFQbbsO1Vs0JisNIEHU UG9MDXvk+i9SxpFeLC0v8hSMYy643cldGnkCd5XdxKqb9g4UJtioveCpf8lEAJCJigJu dD0vI1LimBsyEXENOoQ/wyZZVeTzw9jSannoAELcc2oGnP2rVVqU2M263UvWNoud5a2P 81YIh7UbgJZypi2tGibHdAHMLri8TzwKFJfz4W6QITchQ4+8O+XqGmgxx9lwjxWXTOXa kjqamZZIExPliK25adChINuyG2kEeQj3QvI4S8WlN0vwe9x+jHkhoOwlNVR/bRz1FV0s gZBA== X-Gm-Message-State: ALoCoQkNfAb9xnSHX+4ca+mZNjg3IgN9ayGzOtF03KWP8gnqsOPfDuYuL+LUPBUsyxyROrS1/4O8 MIME-Version: 1.0 X-Received: by 10.55.31.133 with SMTP id n5mr18756737qkh.72.1432577065418; Mon, 25 May 2015 11:04:25 -0700 (PDT) Received: by 10.140.16.97 with HTTP; Mon, 25 May 2015 11:04:25 -0700 (PDT) In-Reply-To: References: <20150525104420.GO8680@tpx> Date: Mon, 25 May 2015 21:04:25 +0300 Message-ID: Subject: Re: IGFS From: Vladimir Ozerov To: dev@ignite.incubator.apache.org Content-Type: multipart/alternative; boundary=001a1147d52019211e0516ebd7a9 --001a1147d52019211e0516ebd7a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I already raised question about backups several months ago but no implementation decisions were made. I am not aware of any architectural problems preventing us form having backups, but currently backups is prohibited eplicitly, and user will get validation error if backup is configured on data cache. However, this makes sense in the most common use case - IGFS as a caching layer over some perstent file system. On Mon, May 25, 2015 at 7:07 PM, Dmitriy Setrakyan wrote: > On Mon, May 25, 2015 at 7:18 AM, Vladimir Ozerov > wrote: > > > Koert, > > > > IGFS stores data in-memory. When using IGFS in pure in-memory mode, no > > failover exists and data can be lost in case one of data nodes leaves t= he > > grid. > > When secondary file system is used (e.g. HDFS), then Ignite is able to > > transparently re-read lost data chunks from the underlying file system. > > > > Is this factually correct? Why can't I configure backups, just like with > regular data grids? > > > > > > Vladimir. > > > > On Mon, May 25, 2015 at 1:44 PM, Konstantin Boudnik > > wrote: > > > > > Can anyone comment on this? Seems like an interesting topic, for sure= . > > > > > > Thanks, > > > Cos > > > > > > On Sun, May 17, 2015 at 12:49AM, Koert Kuipers wrote: > > > > "One of the unique capabilities of Ignite is a file system interfac= e > to > > > its > > > > in-memory data called Ignite File System (IGFS). IGFS delivers > similar > > > > functionality to Hadoop HDFS, but only in memory. In fact, IGFS is = at > > the > > > > core of Ignite=E2=80=99s In-Memory Hadoop Accelerator." > > > > > > > > if IGFS delivers functionality similar to HDFD, then fault toleranc= e > > > would > > > > be one of the most important features. yet i cannot find any mentio= n > of > > > it. > > > > can someone explain? thanks! > > > > > > --001a1147d52019211e0516ebd7a9--