Re: Ignite Transactions and non-committed entries

2016-07-25 Thread vkulichenko 
There are operations that are enlisted in a transaction (get, put, remove,
etc.) and non-transactional (like size, clear, etc.). JavaDoc for methods
usually specify that. If a transactional operation is executed without a
transaction, an implicit transaction will be created by Ignite for this
single operation. Non-transactional operations are always executed outside
of the transactional context, regardless of weather explicit transaction
exists in the current thread or not.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Transactions-and-non-committed-entries-tp6451p6519.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Transactions and non-committed entries

2016-07-22 Thread Juan Velez 
Hi Val,

Thanks for the reply. So if I understand correctly, if a cache is defined to be 
transactional, all accesses to the cache (either a put, get, size, clear, etc.) 
have to be within the context of a transaction?

Thanks - J


> On 22 Jul, 2016, at 2:45 PM, vkulichenko <valentin.kuliche...@gmail.com> 
> wrote:
> 
> Hi,
> 
> size() is not a transactional operation, so it doesn't provide any
> transactional guarantees. Ignite simply maintains an internal counter and
> returns its value from this method.
> 
> -Val
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-Transactions-and-non-committed-entries-tp6451p6485.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Ignite Transactions and non-committed entries

2016-07-21 Thread juanavelez 
b35d34, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
172.19.131.36], sockAddrs=[/172.19.131.36:0, /0:0:0:0:0:0:0:1:0,
/127.0.0.1:0, /172.19.131.36:0], discPort=0, order=10, intOrder=8,
lastExchangeTime=1469140504226, loc=false, ver=1.6.0#20160518-sha1:0b22c45b,
isClient=true]
Jul 21, 2016 3:35:04 PM org.apache.ignite.logger.java.JavaLogger info
INFO: Topology snapshot [ver=10, servers=4, clients=2, CPUs=24, heap=11.0GB]
Jul 21, 2016 3:35:04 PM com.juan.ignite.ClientIgnite main
INFO: Size=0
Jul 21, 2016 3:35:06 PM com.juan.ignite.ClientIgnite main
INFO: Size=309
Jul 21, 2016 3:35:08 PM com.juan.ignite.ClientIgnite main
INFO: Size=679
Jul 21, 2016 3:35:10 PM com.juan.ignite.ClientIgnite main
INFO: Size=1000
Jul 21, 2016 3:35:12 PM org.apache.ignite.logger.java.JavaLogger info
INFO: Your version is up to date.
Jul 21, 2016 3:35:12 PM com.juan.ignite.ClientIgnite main
INFO: Size=1000
Jul 21, 2016 3:35:14 PM com.juan.ignite.ClientIgnite main
INFO: Size=1000
Jul 21, 2016 3:35:16 PM com.juan.ignite.ClientIgnite main
INFO: Size=1000
Jul 21, 2016 3:35:18 PM com.juan.ignite.ClientIgnite main
INFO: Size=1000
Jul 21, 2016 3:35:21 PM com.juan.ignite.ClientIgnite main
INFO: Size=1000
Jul 21, 2016 3:35:21 PM org.apache.ignite.logger.java.JavaLogger info
INFO: Node left topology: TcpDiscoveryNode
[id=69547ec4-f2b9-4365-85cf-bc7f64b35d34, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
172.19.131.36], sockAddrs=[/172.19.131.36:0, /0:0:0:0:0:0:0:1:0,
/127.0.0.1:0, /172.19.131.36:0], discPort=0, order=10, intOrder=8,
lastExchangeTime=1469140504226, loc=false, ver=1.6.0#20160518-sha1:0b22c45b,
isClient=true]
Jul 21, 2016 3:35:21 PM org.apache.ignite.logger.java.JavaLogger info
INFO: Topology snapshot [ver=11, servers=4, clients=1, CPUs=24, heap=7.6GB]
Jul 21, 2016 3:35:23 PM com.juan.ignite.ClientIgnite main
INFO: Size=0
Jul 21, 2016 3:35:25 PM com.juan.ignite.ClientIgnite main
INFO: Size=0




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Transactions-and-non-committed-entries-tp6451.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.