Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 08727200C0E for ; Wed, 1 Feb 2017 23:05:38 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 07146160B46; Wed, 1 Feb 2017 22:05:38 +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 753EB160B41 for ; Wed, 1 Feb 2017 23:05:37 +0100 (CET) Received: (qmail 32379 invoked by uid 500); 1 Feb 2017 22:05:36 -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 32369 invoked by uid 99); 1 Feb 2017 22:05:36 -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, 01 Feb 2017 22:05:36 +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 2AC1E1A051C for ; Wed, 1 Feb 2017 22:05:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 2muJFaNdIR7d for ; Wed, 1 Feb 2017 22:05:31 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C4ACC5F30D for ; Wed, 1 Feb 2017 22:05:30 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id E7B8D3BC742A for ; Wed, 1 Feb 2017 13:46:19 -0800 (PST) Date: Wed, 1 Feb 2017 15:05:29 -0700 (MST) From: ignite_user2016 To: user@ignite.apache.org Message-ID: <1485986729579-10366.post@n6.nabble.com> In-Reply-To: <1485982863638-10363.post@n6.nabble.com> References: <1485973543960-10361.post@n6.nabble.com> <1485982863638-10363.post@n6.nabble.com> Subject: Re: Ignite as a shared file sysytem MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Wed, 01 Feb 2017 22:05:38 -0000 Thank you for the response. http://apache-ignite-users.70518.x6.nabble.com/IGFS-backed-by-persistence-on-physical-filesystem-td1882.html I am just wondering this thread does talk about file system shared between web apps ? my use case is simple - build a file system that can be shared across web app deployed in cluster environment Do you still think it would be overkill ? of course, we dont want to go in HDFS route at all. Regards, Rishi -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-as-a-shared-file-sysytem-tp10361p10366.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.