Abstract
In MySQL 5.7 and earlier, metadata locks were often a source of confusion. The problem is that it is not obvious who holds the metadata lock. In MySQL 5.7, instrumentation of the metadata locks was added to the Performance Schema, and in MySQL 8.0, it is enabled by default. With the instrumentation enabled, it becomes easy to determine who is blocking the connection trying to obtain the lock. This chapter goes through an example of a situation with metadata locks and examines it. First the symptoms are discussed.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2021 Jesper Wisborg Krogh
About this chapter
Cite this chapter
Krogh, J.W. (2021). Case Study: Metadata and Schema Locks. In: MySQL Concurrency. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-6652-6_14
Download citation
DOI: https://doi.org/10.1007/978-1-4842-6652-6_14
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-6651-9
Online ISBN: 978-1-4842-6652-6
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books