From dev-return-46311-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Jun 17 15:29:47 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 9FFAE18076D for ; Mon, 17 Jun 2019 17:29:47 +0200 (CEST) Received: (qmail 2020 invoked by uid 500); 17 Jun 2019 15:29:47 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 2009 invoked by uid 99); 17 Jun 2019 15:29:46 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jun 2019 15:29:46 +0000 Received: from mail-wm1-f42.google.com (mail-wm1-f42.google.com [209.85.128.42]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 0D1A88BD7 for ; Mon, 17 Jun 2019 15:29:46 +0000 (UTC) Received: by mail-wm1-f42.google.com with SMTP id z23so9584917wma.4 for ; Mon, 17 Jun 2019 08:29:45 -0700 (PDT) X-Gm-Message-State: APjAAAV6XXVcnmLInVfDd45WBWHDKvqLQCp6z7lUKcBj9M6mnLI3cfou SOzSWyYAWZlfgqwyVOPSyXIx02OVASMQP18l14M= X-Google-Smtp-Source: APXvYqxP6uw5AusuabouhHLcu1QAgLpseKN6cXvzZ3a6R3R0RWu8QivO3lyS0Jh+YUjVbKedVbjo2lEbJfatX49Week= X-Received: by 2002:a7b:c776:: with SMTP id x22mr19091402wmk.55.1560785385290; Mon, 17 Jun 2019 08:29:45 -0700 (PDT) MIME-Version: 1.0 References: <9e79999ffe5b00d829260760ea6048de63288eec.camel@gmail.com> In-Reply-To: From: Dmitriy Pavlov Date: Mon, 17 Jun 2019 18:29:35 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DISCUSSION] Complete Discontinuation of IGFS and Hadoop Accelerator To: dev Content-Type: multipart/alternative; boundary="00000000000076017d058b86aa45" --00000000000076017d058b86aa45 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Igniters, +1 from me provided that we move sources to some supplementary repository. If someone later would like to maintain/fix this module, he/she should be able to access sources with current state of the master. Sincerely, Dmitriy Pavlov =D0=BF=D0=BD, 17 =D0=B8=D1=8E=D0=BD. 2019 =D0=B3. =D0=B2 18:25, Igor Sapego= : > +1 from me. Hadoop Accelerator seems like an outdated solution, > and I believe IGFS was only added to support Hadoop Accelerator. > > Best Regards, > Igor > > > On Mon, Jun 17, 2019 at 12:00 PM Nikolay Izhikov > wrote: > > > +1 from me to reduce supported feature list. > > > > Guys, are we talking about Ignite 3.0? > > > > > > =D0=92 =D0=9F=D0=BD, 17/06/2019 =D0=B2 11:57 +0300, Alexey Goncharuk = =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > > Denis, > > > > > > I fully support this idea. > > > > > > First, looking back, I do not think it was a good design in the first > > place > > > to build IGFS on top of Ignite caches. Second, I have never seen a ca= se > > > where IGFS provided significant performance boost. Usually it's eithe= r > > all > > > data already fits buffer cache, and IGFS caching is not needed; or da= ta > > > does not fit buffer cache, and access pattern is close to full scan a= nd > > > additional caching in IGFS does not make sense. > > > > > > =D0=BF=D0=BD, 17 =D0=B8=D1=8E=D0=BD. 2019 =D0=B3. =D0=B2 11:28, =D0= =9F=D0=B0=D0=B2=D0=BB=D1=83=D1=85=D0=B8=D0=BD =D0=98=D0=B2=D0=B0=D0=BD : > > > > > > > Denis, > > > > > > > > I must say that aforementioned solutions for a Hadoop ecosystem > appear > > > > from time to time in questions on a user mailing list. So, it seems > > > > that there is a practical need for such solutions. > > > > > > > > But of course it does not mean that we should continue a support of > > > > IGFS and Hadoop Accelerator. If both are not solutions that fit wel= l > > > > common use cases then we should discontinue it. If any of them is > very > > > > good for it's purposes but we do not have a capacity to support it > > > > without sacrificing main Ignite goals then we still should > discontinue > > > > it in my mind. > > > > > > > > P.S. Personally I am a fan of UNIX way. I like ideas of a single > > > > responsibility and integrations. And I suppose there are other Igni= te > > > > features which could be dropped. > > > > > > > > =D1=81=D1=80, 12 =D0=B8=D1=8E=D0=BD. 2019 =D0=B3. =D0=B2 21:04, Den= is Magda : > > > > > > > > > > > > > > Igniters, > > > > > > > > > > I'd like us to move on and finish our conversation on the IGFS [1= ] > > and > > > > > Hadoop Accelerator [2] support. > > > > > > > > > > To my knowledge, there is no single committer who maintains the > > > > > integrations; they are no longer tested and, even more, the > community > > > > > stopped providing the binaries since Ignite 2.6.0 release (look f= or > > > > > In-Memory Hadoop Accelerator table [3]). > > > > > > > > > > Why all of that happened? Because of a little value, something > > succeeds > > > > > while something fails. Does it mean that Ignite cannot be used fo= r > > Hadoop > > > > > acceleration, in general? No, quite the opposite, it CAN be used, > > but a > > > > > solution is different. Have Ignite with native persistence deploy= ed > > close > > > > > to your Hadoop cluster (replace GridGain with Ignite) [4]. > > > > > > > > > > So, I propose we remove IGFS and In-Memory Hadoop Accelerator fro= m > > our > > > > > master repository and rework existing public documentation showin= g > > how to > > > > > achieve the acceleration with Ignite. > > > > > > > > > > Any supporters or objections? > > > > > > > > > > > > > > > [1] https://apacheignite-fs.readme.io/docs/in-memory-file-system > > > > > [2] https://apacheignite-fs.readme.io/docs/hadoop-accelerator > > > > > [3] https://ignite.apache.org/download.cgi#binaries > > > > > [4] > > > > > > > > > > > > > > > > https://docs.gridgain.com/docs/bdb-getting-started#section-gridgain-data-= lake-accelerator > > > > > > > > > > - > > > > > Denis > > > > > > > > > > > > > > > > -- > > > > Best regards, > > > > Ivan Pavlukhin > > > > > > > --00000000000076017d058b86aa45--