ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Atri Sharma <atri.j...@gmail.com>
Subject Re: Cross cache transactional coherency
Date Fri, 05 Jun 2015 09:16:39 GMT
In context to:

http://mail-archives.apache.org/mod_mbox/ignite-dev/201504.mbox/%3CCAOeZVicFf2DLTqhg-LG96y4VuCjia9yFm47PtvaGYVbQ-K6RQw@mail.gmail.com%3E

On Fri, Jun 5, 2015 at 1:43 AM, Alexey Goncharuk <alexey.goncharuk@gmail.com
> wrote:

> Hello Atri,
>
> What corruption issue are you talking about? Is there a corresponding
> ticket?
>
> As for the transaction-related code, it has a lot of classes and the Base
> would differ depending on what you want to look at. From the top of my
> head, the main logic is concentrated in the following classes:
>
>    - IgniteTxAdapter and it's inheritors contain all the state related to
>    an ongoing transaction (including transaction on near, primary and
> backup
>    nodes)
>    - Grid*LockFuture classes contain logic related to entries locking in
>    pessimistic mode
>    - Grid*TxPrepareFuture classes contain logic related to the prepare step
>    of a transaction
>    - Grid*TxFinishFuture classes contain logic related to the finish step
>    of a transaction
>    - IgniteTxManager and IgniteTxHandler contain logic that wire up various
>    transaction steps
>
> Let me know if you have more specific questions, I will be happy to walk
> you through the code.
>
> --AG
>
> 2015-06-04 12:46 GMT-07:00 Atri Sharma <atri.jiit@gmail.com>:
>
> > Folks,
> >
> > I remember a conversation we had about cross cache transactional
> > coherency.  I remember Vladimir mentioning we have support for that from
> > 1.0.0. Can anyone please point me to the required code Base?  I am trying
> > to hack a solution for the corruption issue when node is abruptly
> stopped.
> >
> > Regards,
> >
> > Atri
> >
>



-- 
Regards,

Atri
*l'apprenant*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message