Ignite's lock acquisition depends on the transaction isolation. AFAIK, read_commited and optimistic modes do not lock entries on read. Ignte has no meaning of read-only cache and I doubt it will have in future, but you can try to ask on the dev list.
As a workaround, you can create local ConcurrentHashMap and populate it with static data using the broadcast job [1] on cluster startup. [1] See javadoc for ignite.compute().broadcast() 2016-05-30 17:52 GMT+03:00 amitpa <[email protected]>: > Ignore my latest question . This seems to work fine. > > I have one kind of feature request though. > > It seems with transaction, Ignite always tries to get the lock for the keys > accessed. > However some caches can be read only. Multiple transactions can access the > same key, but they will never modify it. > > Is there any way to mark a cache as read only and hence exempt for > transaction lock acquiring, this I believe is a common case for things like > reference data. This will also help in throughput for most applications > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Affinity-Key-Mapping-tp5212p5321.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Best regards, Alexei Scherbakov
