This document is DEPRECATED.

Please consider any information here as out of date. DO NOT use this document.

Instead, refer to

Please update your bookmarks accordingly.

Skip to end of metadata
Go to start of metadata

REPEATABLE_READ is one of two isolation levels the Infinispan's locking infrastructure provides (the other is READ_COMMITTED). Isolation levels have their origins in database.

In Infinispan, REPEATABLE_READ works slightly differently to databases. REPETEABLE_READ says that "data can be read as long as there are no writes, and viceversa". This avoids the non-repeatable reads phenomenon, because once data has been written, no other transaction can read it, so there's no chance of re-reading the data and finding different data.

However, as indicated in READ_COMMITTED article, Infinispan has an MVCC model that allows it to have non-blocking reads. Infinispan provides REPETEABLE_READ semantics by keeping the previous value whenever an entry is modified. This allows Infinispan to retrieve the previous value if a second read happens within the same transaction.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.