Hello There!

We have recently started using Apache Ignite 2.1.0 data grid cache with
Cassandra as backend datastore. Related to the transaction management, I
have few confusions and hence would like to get some expert advice from
your end in this approach.

We have a small Ignite integration component which is responsible for
performing Ignite interactions as client in multiple threads. To do that,
we have two approaches:

(1) Each thread should have its own Ignite object should start the
transaction independently from the same Ignite object
(2) A centralized shared Ignite object can be created and each thread can
obtain an IgniteTransaction object from the same Ignite object to manage
transactions independently.

We prefer to go with option (2) as Ignite object itself is heavy, which
creates multiple internal threads and also takes some memory. Hence If I
have a system running with 100 threads, creating 100 independent Ignite
object seems to be quite costly as system resource crunching!

I have gone through a number of discussions related to this in this user
group, but end of the day got a bit of confusion as :

(1) Many link talks about Ignite object being thread safe and is designed
to be used in shared mode, giving transaction control at thread level. In
fact I have seen Transaction class details where current thread id is also
captured - where can I get some information on how threads and transactions
are related?
(2) There are also mailing threads stating nested transactions are not
supported. What do we mean by nested transaction? Does this mean that under
a single Ignite object, only one transaction can be active at a given point
of time? But if this is true, it contradicts to the fact mentioned above.

Any help, document link, understanding the association between threads,
Ignite Object and Transactions would be really helpful! Also please share
if we have any kind of restrictions available which I may be missing.


<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Reply via email to