Re: Safe locking for multiple nodes and updates.
There will be occasional collisions. Usually, rather than the preventive locking you describe, it's better to write the update code in a transaction with rollback and retry logic to handle deadlocks and other such problems gracefully. It's called optimistic concurrency.
Subject
Written By
Posted
Re: Safe locking for multiple nodes and updates.
March 03, 2019 12:28AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.