Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <3B50100E-E8D5-4712-A1A5-5378EC660697@apache.org>
References: <CABuYRcoGMj89dDt5pfnxNvT5UGyHA0beZv+EKZy0KrjhuX3VAg@mail.gmail.com>
 <3B50100E-E8D5-4712-A1A5-5378EC660697@apache.org>
From: Valentin Kulichenko <valentin.kulichenko@gmail.com>
Date: Fri, 1 Dec 2017 12:41:22 -0800
Message-ID: <CABuYRcpq0wD63BNzqcMTwoT2WnWH8=NoCKBS6H69zjfSeGdGHQ@mail.gmail.com>
Subject: Re: Deprecate IgniteRDD in embedded mode
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="94eb2c1245200c91cc055f4d66d6"
archived-at: Fri, 01 Dec 2017 20:42:04 -0000

--94eb2c1245200c91cc055f4d66d6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Ticket created: https://issues.apache.org/jira/browse/IGNITE-7092

-Val

On Thu, Nov 30, 2017 at 5:01 PM, Denis Magda <dmagda@apache.org> wrote:

> Val,
>
> Sounds reasonable to me. The fewer useless and potentially harmful
> features or =E2=80=9Cswitches=E2=80=9D we have in Ignite the clear it wil=
l be for the user
> how to use us in a right way.
>
> +1 for the deprecation and further removal.
>
> =E2=80=94
> Denis
>
> > On Nov 30, 2017, at 3:07 PM, Valentin Kulichenko <
> valentin.kulichenko@gmail.com> wrote:
> >
> > Igniters,
> >
> > Currently we claim to support IgniteRDD in two modes: standalone and
> > embedded. Standalone means there is a separately running Ignite cluster=
,
> > and Spark start client node(s) to interact with it. In embedded node
> > everything runs within Spark, including Ignite server nodes that are
> > started embedded into Spark executors.
> >
> > The latter case doesn't really work, mainly because the lifecycle of
> Spark
> > executors is not very predictable - Spark can start and stop them while
> > application is running. In case Ignite cluster is used to store data
> (which
> > is usually the case), this causes unnecessary rebalancing or even
> > unexpected data loss.
> >
> > I propose to deprecate and eventually discontinue the embedded mode.
> > Luckily, standalone mode is the default one, so we can simply print out=
 a
> > clear warning if one switches to embedded mode, and also mention this i=
n
> > the docs.
> >
> > Thoughts? If there are no objections, I will create a ticket and make t=
he
> > change.
> >
> > -Val
>
>

--94eb2c1245200c91cc055f4d66d6--