Red Hat Summitこのコンテンツは選択した言語では利用できません。
14.3. Locking Types
14.3.1. About Optimistic Locking
リンクのコピーリンクがクリップボードにコピーされました!
Optimistic locking allows multiple transactions to complete simultaneously by deferring lock acquisition to the transaction prepare time.
Optimistic mode assumes that multiple transactions can complete without conflict. It is ideal where there is little contention between multiple transactions running concurrently, as transactions can commit without waiting for other transaction locks to clear. With
writeSkewCheck enabled, transactions in optimistic locking mode roll back if one or more conflicting modifications are made to the data before the transaction completes.
14.3.2. About Pessimistic Locking
リンクのコピーリンクがクリップボードにコピーされました!
Pessimistic locking is also known as eager locking.
Pessimistic locking prevents more than one transaction to modify a value of a key by enforcing cluster-wide locks on each write operation. Locks are only released once the transaction is completed either through committing or being rolled back.
Pessimistic mode is used where a high contention on keys is occurring, resulting in inefficiencies and unexpected roll back operations.
14.3.3. Pessimistic Locking Types
リンクのコピーリンクがクリップボードにコピーされました!
Red Hat JBoss Data Grid includes explicit pessimistic locking and implicit pessimistic locking:
- Explicit Pessimistic Locking, which uses the JBoss Data Grid Lock API to allow cache users to explicitly lock cache keys for the duration of a transaction. The Lock call attempts to obtain locks on specified cache keys across all nodes in a cluster. This attempt either fails or succeeds for all specified cache keys. All locks are released during the commit or rollback phase.
- Implicit Pessimistic Locking ensures that cache keys are locked in the background as they are accessed for modification operations. Using Implicit Pessimistic Locking causes JBoss Data Grid to check and ensure that cache keys are locked locally for each modification operation. Discovering unlocked cache keys causes JBoss Data Grid to request a cluster-wide lock to acquire a lock on the unlocked cache key.
14.3.4. Explicit Pessimistic Locking Example
リンクのコピーリンクがクリップボードにコピーされました!
The following is an example of explicit pessimistic locking that depicts a transaction that runs on one of the cache nodes:
Procedure 14.3. Transaction with Explicit Pessimistic Locking
tx.begin() cache.lock(K) cache.put(K,V5) tx.commit()
tx.begin()
cache.lock(K)
cache.put(K,V5)
tx.commit()- When the line
cache.lock(K)executes, a cluster-wide lock is acquired onK. - When the line
cache.put(K,V5)executes, it guarantees success. - When the line
tx.commit()executes, the locks held for this process are released.
14.3.5. Implicit Pessimistic Locking Example
リンクのコピーリンクがクリップボードにコピーされました!
An example of implicit pessimistic locking using a transaction that runs on one of the cache nodes is as follows:
Procedure 14.4. Transaction with Implicit Pessimistic locking
tx.begin() cache.put(K,V) cache.put(K2,V2) cache.put(K,V5) tx.commit()
tx.begin()
cache.put(K,V)
cache.put(K2,V2)
cache.put(K,V5)
tx.commit()- When the line
cache.put(K,V)executes, a cluster-wide lock is acquired onK. - When the line
cache.put(K2,V2)executes, a cluster-wide lock is acquired onK2. - When the line
cache.put(K,V5)executes, the lock acquisition is non operational because a cluster-wide lock forKhas been previously acquired. Theputoperation will still occur. - When the line
tx.commit()executes, all locks held for this transaction are released.
14.3.6. Configure Locking Mode (Remote Client-Server Mode)
リンクのコピーリンクがクリップボードにコピーされました!
To configure a locking mode in Red Hat JBoss Data Grid's Remote Client-Server mode, use the
transaction element as follows:
<transaction locking="{OPTIMISTIC/PESSIMISTIC}" />
<transaction locking="{OPTIMISTIC/PESSIMISTIC}" />14.3.7. Configure Locking Mode (Library Mode)
リンクのコピーリンクがクリップボードにコピーされました!
In Red Hat JBoss Data Grid's Library mode, the locking mode is set within the
transaction element as follows:
<transaction transactionManagerLookupClass="{TransactionManagerLookupClass}"
transactionMode="{TRANSACTIONAL,NON_TRANSACTIONAL}"
lockingMode="{OPTIMISTIC,PESSIMISTIC}"
useSynchronization="true">
</transaction>
<transaction transactionManagerLookupClass="{TransactionManagerLookupClass}"
transactionMode="{TRANSACTIONAL,NON_TRANSACTIONAL}"
lockingMode="{OPTIMISTIC,PESSIMISTIC}"
useSynchronization="true">
</transaction>
Set the
lockingMode value to OPTIMISTIC or PESSIMISTIC to configure the locking mode used for the transactional cache.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}