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 4D7D0183B8 for ; Mon, 14 Sep 2015 09:20:42 +0000 (UTC) Received: (qmail 7822 invoked by uid 500); 14 Sep 2015 09:20:42 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 7781 invoked by uid 500); 14 Sep 2015 09:20:42 -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 7771 invoked by uid 99); 14 Sep 2015 09:20:42 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Sep 2015 09:20:42 +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 AB9E4F207E for ; Mon, 14 Sep 2015 09:20:41 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.999 X-Spam-Level: ** X-Spam-Status: No, score=2.999 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id suhgo9xFnI91 for ; Mon, 14 Sep 2015 09:20:35 +0000 (UTC) Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com [209.85.192.47]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 0B0C542B78 for ; Mon, 14 Sep 2015 09:20:35 +0000 (UTC) Received: by qgx61 with SMTP id 61so109680660qgx.3 for ; Mon, 14 Sep 2015 02:20:34 -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=l7IVsuLUshl25JEO9W9LlVLTuGNxgp69AK3v08mnZcg=; b=Rz/ksz4PhQG+j9oPpLJh+/r0u3TPEpgIMaRXGA3i4slGu80lkdk+K9aWY7go2SckwQ qFUQvY7RMXktgcGcYxB0w8K8f8Ue4qhaPddGKIuw7XixKi40zO/rqLM+fG4DoK12/hh0 ulr5VKrIfM7vVM/wpwwQzMpmTMVG3ns7ySZJ4bUmUaOcGbH4a6RUlrEKesgJizrE/qlx PHj/fgI5K/iaptJK8z8Flypq2zuVepcBfENJbaxiuN2mssKHJMcjoxdekhfQdYbVcXRV W/kD8hC7t6m0szPLVq0su6xsbiLviCtsniOao7GSoS2mV6h89kU/gEcRysHV1J4TK5hI dHZw== X-Gm-Message-State: ALoCoQn0r3Q4zmGYANO0Iwda4tD92oPK0iKIwI10pQrWZ7HvBmY8zPLlqMo/Zy0IYiqFSo4OFjEn MIME-Version: 1.0 X-Received: by 10.140.216.202 with SMTP id m193mr21469487qhb.30.1442222434661; Mon, 14 Sep 2015 02:20:34 -0700 (PDT) Received: by 10.140.20.167 with HTTP; Mon, 14 Sep 2015 02:20:34 -0700 (PDT) In-Reply-To: <1442220999059-1378.post@n6.nabble.com> References: <1441349269988-1273.post@n6.nabble.com> <1441754212208-1302.post@n6.nabble.com> <1441863204725-1331.post@n6.nabble.com> <1441875130227-1336.post@n6.nabble.com> <1441973378556-1360.post@n6.nabble.com> <1441974090158-1361.post@n6.nabble.com> <1442216682993-1375.post@n6.nabble.com> <1442220999059-1378.post@n6.nabble.com> Date: Mon, 14 Sep 2015 12:20:34 +0300 Message-ID: Subject: Re: How to configure Hadoop accelerator for Hadoop-High Availability ? From: Vladimir Ozerov To: user@ignite.apache.org Content-Type: multipart/alternative; boundary=001a1135ae22e7e736051fb19365 --001a1135ae22e7e736051fb19365 Content-Type: text/plain; charset=UTF-8 Jesu, Yes, normally we expect that one Ignite node will run on all machines where file system is accessed. The main reason for this is performance. For example, what if Hadoop sent a job to a node where HDFS is running, but there is no Ignite node? In this case if you access HDFS through IGFS, you will have to connect to some remote Ignite node and try fetching data form there, what is less than optimal due to additoinla network trips. This is why advised way to work with IGFS is to start Ignite node on each machine running HDFS. However, this is not strict requirement. You can work with remote Ignite nodes through TCP endpoint of course. But if IGFS use some additional Hadoop configuration files like *core-site.xml* or *hdfs-site.xml*, then you must ensure that they are placed in the same directories on all machnies where you access IGFS. Please let me know if you have any further questions. Vladimir. On Mon, Sep 14, 2015 at 11:56 AM, Jesu wrote: > Vladimir, > Yes, the processes are running in different machines. Does this mean ignite > needs to run on all the machines in which igfs is accessed? > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/How-to-configure-Hadoop-accelerator-for-Hadoop-High-Availability-tp1273p1378.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > --001a1135ae22e7e736051fb19365 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Jesu,

Yes, normally we expect that one = Ignite node will run on all machines where file system is accessed. The mai= n reason for this is performance. For example, what if Hadoop sent a job to= a node where HDFS is running, but there is no Ignite node? In this case if= you access HDFS through IGFS, you will have to connect to some remote Igni= te node and try fetching data form there, what is less than optimal due to = additoinla network trips. This is why advised way to work with IGFS is to s= tart Ignite node on each machine running HDFS.

How= ever, this is not strict requirement. You can work with remote Ignite nodes= through TCP endpoint of course. But if IGFS use some additional Hadoop con= figuration files like core-site.xml or hdfs-site.xml, then yo= u must ensure that they are placed in the same directories on all machnies = where you access IGFS.=C2=A0

Please let me know if= you have any further questions.

Vladimir.


On Mon, Sep 14, 2015 at 11:56 AM, Jesu <jesu.i.das@gmail.com><= /span> wrote:
Vladimir,
Yes, the processes are running in different machines. Does this mean ignite=
needs to run on all the machines in which igfs is accessed?



--
View this message in context: http://apache-ign= ite-users.70518.x6.nabble.com/How-to-configure-Hadoop-accelerator-for-Hadoo= p-High-Availability-tp1273p1378.html
Sent from the Apache Ignite Users m= ailing list archive at Nabble.com.

--001a1135ae22e7e736051fb19365--