Abstract
The Two-Phase Locking of Multi-Version Concurrency Control (MV2PL) avoids conflicts of concurrent transactions by make them wait until conflicts get resolved. These conflicts of transactions may generate starvations and deadlocks in the system. The Transactions suffering from deadlocks are usually aborted and restarted from scratch. In multiuser systems, this “abort and restart” approach degrades the system’s performance where higher conflicts for data or long running transactions occur. Restarting from scratch also generates a negative response loop in the system, because the system suffers additional overheads which may result into even more conflicts. In this paper, we are proposing a novel approach for conflict resolution in Multi-Version Concurrency Control for shared databases. Our mechanism quickly detects the conflicts using correctness criteria for serializability and resolves the conflicts between transactions and increases throughput.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Innovative Technology and Exploring Engineering
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
