Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
References: <CAKr8LfykAsf1taj8Q1AbL9g0WnwPTJR8YvQXsKk5eq7mAZXpDQ@mail.gmail.com>
 <CAGcMBHg-8rsAcbevB9+VmNt4DBSQZuH4cNreQLXOL2JmUvCE-g@mail.gmail.com>
 <CAKr8Lfxmeou9rDC7tpaqnRmysjMitviF33nBn8XnTzP7wnfRzA@mail.gmail.com>
 <CAGcMBHjL5gsDAnR0DDwP_SDPGs28mKy67GDXadUuuOo+yz0W+w@mail.gmail.com>
 <CAKr8LfxNwPQLsLf3yHVRw_-nf9+PWyGGD8Uyz_bk_nEinPL5tA@mail.gmail.com>
 <CAGcMBHjGWP7ko0DCCMikhia25aqjOzTO-d36CCK66rOMM2-ZLQ@mail.gmail.com>
 <CAKr8LfytzNMLPpX9Mi7mx0sPad5dC-x9kLfnZ7UoakArxJV2tg@mail.gmail.com> <CAGcMBHicnUvazEhMLetbm+2=PEthsWxFo4Dn1Ae-c3gApPYFfw@mail.gmail.com>
In-Reply-To: <CAGcMBHicnUvazEhMLetbm+2=PEthsWxFo4Dn1Ae-c3gApPYFfw@mail.gmail.com>
From: ALEKSEY KUZNETSOV <alkuznetsov.sb@gmail.com>
Date: Mon, 03 Jul 2017 13:56:24 +0000
Message-ID: <CAKr8Lfzxp-qWvpkjrcQS1VpqK1mYu1qooDAu1dypm7FT5gk_EQ@mail.gmail.com>
Subject: Re: Support for starting transaction in another thread IGNITE-4887
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="001a11442c2a92698d05536a224d"
archived-at: Mon, 03 Jul 2017 13:56:42 -0000

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

It is a global scope) Now multiple threads can commit transaction and it
will lead to exception. It doesn't refer to my ticket only, but for a
current transaction implementation.

=D0=BF=D0=BD, 3 =D0=B8=D1=8E=D0=BB. 2017 =D0=B3. =D0=B2 16:53, Yakov Zhdano=
v <yzhdanov@apache.org>:

> What separate ticket do you mean here? I think this is the scope of the
> original one.
>
> --Yakov
>
> 2017-07-03 16:39 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov.sb@gmail.com>:
>
> > I've go a test, which illustrates transaction commit fail when multiple
> > threads try to commit. As i said, it happenes in mvcc stage.
> >
> > So we should create a special lock mechanism for all transaction method=
s.
> > In a separate ticket.
> >
> > =D0=BF=D0=BD, 3 =D0=B8=D1=8E=D0=BB. 2017 =D0=B3. =D0=B2 16:26, Yakov Zh=
danov <yzhdanov@apache.org>:
> >
> >> >Consider thread *Th1* started transaction *Tx1*, done some actions, a=
nd
> >> is
> >> >calling commit (GridNearTxLocal#commit -> commitNearTxLocalAsync). An=
d
> >> >concurrently thread *Th2 *is calling the same commit on* Tx1*.
> >>
> >> Alexey, this looks weird to me. IMO, if we talk about proper
> >> implementation
> >> you should detect all cases of illegal access (e.g. commit from thread
> not
> >> owning the transaction).
> >>
> >> --Yakov
> >>
> > --
> >
> > *Best Regards,*
> >
> > *Kuznetsov Aleksey*
> >
>
--=20

*Best Regards,*

*Kuznetsov Aleksey*

--001a11442c2a92698d05536a224d--