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: <CAB_oYF_783np98vZF+pMA0CzN4j1VRQLJBqsDWDqCrtsHmd3pA@mail.gmail.com>
References: <CANdpPsWtqUZByL4+Lw2JJvnU9W1fvAjaqLnKYHpTmCbvE5nWUA@mail.gmail.com>
 <CAB2fC0s+J1XrgH=qfzmUog3vS4NE7wdC_-bVMf3FZzWV71cqjw@mail.gmail.com>
 <CA+0=VoVUkjGaTGxEvh4jzExnLNder6GMxmL69QQ492Rr-Ha3ng@mail.gmail.com>
 <CAMegbcKJPzFYXs=sA4xyfU-oASJB81cZJxL0VJLV0umUwm1n=A@mail.gmail.com> <CAB_oYF_783np98vZF+pMA0CzN4j1VRQLJBqsDWDqCrtsHmd3pA@mail.gmail.com>
From: Dmitriy Setrakyan <dsetrakyan@apache.org>
Date: Fri, 9 Dec 2016 10:45:28 -0800
Message-ID: <CA+0=VoXsFum-qkN7=Xr-oD7t68jYidK22xvX221LY93dQgS4Hw@mail.gmail.com>
Subject: Re: affinityCall in one distributed transaction
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=94eb2c05f920d2543d05433e2a37
archived-at: Fri, 09 Dec 2016 18:46:12 -0000

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

Sounds like you need a centralized JTA server for this type of purpose, no?
In that case, Ignite transactions can already merge into ongoing JTA
transactions.

I would prefer to see a distributed flow of events to fully understand the
issue. For example,

Client
  - start transaction
  - send compute

Server
  - receive compute
  - execute ...
  - execute ...

etc.

D.

On Fri, Dec 9, 2016 at 1:26 AM, =D0=90=D0=BD=D1=82=D0=BE=D0=BD =D0=A7=D1=83=
=D1=80=D0=B0=D0=B5=D0=B2 <churaev.an@gmail.com> wrote:

> In some cases it is necessary to implement a transaction processing logic
> in several different application servers. In this case, working with Igni=
te
> cache will be performed within the various applications. But all these
> changes must be made within the same distributed transaction.
>
> In my opinion this will require context transfer between the threads with=
in
> a single node or multiple Ignite nodes.
>
> 2016-12-08 12:53 GMT+03:00 Alexei Scherbakov <alexey.scherbakoff@gmail.co=
m
> >:
>
> > Hi.
> >
> > It's unclear from your description what are you trying to achieve.
> >
> > AffinityCall is unicast and wil be send to single node.
> >
> > To parallelise task among the cluster I would recommend to use compute
> task
> > API [1]
> >
> > But the task execution is not transactional. Nevertheless, each job
> > triggered by task can use it's own local transaction.
> >
> > And please explain, why can't you use a generic Ignite transaction for
> you
> > task?
> >
> > [1] https://apacheignite.readme.io/docs/compute-tasks
> >
> > 2016-12-08 4:09 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.org>:
> >
> > > Taras, is invokeAll() transactional? The javadoc is silent to this
> fact.
> > If
> > > it is indeed transactional, then we should update the javadoc.
> > >
> > > D.
> > >
> > > On Wed, Dec 7, 2016 at 5:32 AM, Taras Ledkov <tledkov@gridgain.com>
> > wrote:
> > >
> > > > Ignite compute has no relation to the cache's transaction.
> > > >
> > > > I think that IgniteCache.invokeAll() is appropriate for described
> case.
> > > >
> > > > On Wed, Dec 7, 2016 at 4:00 PM, =D0=98=D0=B3=D0=BE=D1=80=D1=8C =D0=
=93 <frenel@gmail.com> wrote:
> > > >
> > > > > Hi, igniters!
> > > > >
> > > > > Before openning JIRA ticket, I want to ask question about
> > affinityCall
> > > or
> > > > > affinityRun transactions.
> > > > >
> > > > > For example I have batch task to modify many values in someCache
> > > > according
> > > > > to someRule. I want to parallel this task to whole cluster and
> > minimize
> > > > > network traffic.
> > > > > So the resonable choice is affinityCall feature.
> > > > >
> > > > > But I want all this changes to be in one transactoin. i.e. with a=
t
> > > least
> > > > > atomicity property (of ACID). And if for some reason my task will
> be
> > > > > canceled or failed on one node - it should change nothing at all.
> > > > >
> > > > > So, can I achieve this with existing functionality, or how can I
> > > approach
> > > > > to this task?
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> >
> > Best regards,
> > Alexei Scherbakov
> >
>
>
>
> --
> =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,
> =D0=A7=D1=83=D1=80=D0=B0=D0=B5=D0=B2 =D0=90=D0=BD=D1=82=D0=BE=D0=BD
>

--94eb2c05f920d2543d05433e2a37--