Multiple choices questions in Distributed database, single lock manager concurrency control in distributed database, What is single lock manager approach? why deadlock handling is simple under single lock manager approach? How does single lock manager approach work?
Distributed database solved MCQ - Why deadlock handling is simple under single lock manager concurrency control protocol in distributed transactions
Next > |
1. Single lock manager approach is a concurrency control mechanism used in distributed database environment. Which of the following is an advantage of the above approach?
(a) Lock manager site is not vulnerable to failure
(b) Handling the deadlock is simple
(c) Implementation of the approach requires multiple messages handling for single transaction
(d) Lock manager site prone to bottleneck
Answer: (b) Handling the deadlock is simple What is single lock manager approach for concurrency control in DDB?As per this approach, the distributed database system maintains a single lock manager at a chosen site S. In distributed database, a transaction can be initiated at any site (server) that is part of the distributed database. Whenever a transaction requires locking a data item, it has to send the lock request to the lock manager site S. Based on the availability of the requested data item, S can grant or delay the lock permission.
Why deadlock handling is simple in single lock manager approach?Deadlocks are possible under lock based concurrency control mechanisms. They can be detected using Wait-for-graph in a centralized database system. Deadlock handling by single lock manager based concurrency control mechanism in distributed database is almost equivalent to that of centralized database system. Hence, handling of deadlock is simple.
Deadlock handling under Single lock manager concurrency control mechanism is simple than that of Distributed lock manager. |
distributed lock manager
Next > |
Related links:
- Go to Distributed Database Quiz page
- Go to Database Management Systems Quiz page
- Go to Distributed Database Home page
No comments:
Post a Comment