DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Data Engineering
  3. Databases
  4. MySQL 5.5 lock_wait_timeout: patience is a virtue, and a locked server

MySQL 5.5 lock_wait_timeout: patience is a virtue, and a locked server

Peter Zaitsev user avatar by
Peter Zaitsev
·
Mar. 01, 13 · Interview
Like (0)
Save
Tweet
Share
4.32K Views

Join the DZone community and get the full member experience.

Join For Free
mysql 5.5 lock_wait_timeout: patience is a virtue, and a locked server

mysql 5.5 lock_wait_timeout: patience is a virtue, and a locked server

this post comes from daniel nichter at the mysql performance blog.

like ovais said in implications of metadata locking changes in mysql 5.5 , the hot topic these days is mysql 5.6, but there was an important metadata locking change in mysql 5.5.  as i began to dig into the percona toolkit bug he reported concerning this change apropos pt-online-schema-change , i discovered something about lock_wait_timeout that shocked me.  from the mysql 5.5 docs for lock_wait_timeout :

this variable specifies the timeout in seconds for attempts to acquire metadata locks. the permissible values range from 1 to 31536000 (1 year). the default is 31536000.

translation: by default, mysql 5.5 will “meta-block” for 1 year!  in my humble opinion, this is a bug, especially given the various subtle and sometimes quiet ways that metadata locking can lock the server as ovais describes in his blog post.  the default for innodb_lock_wait_timeout, by comparison, is 50 seconds.  that’s reasonable, but 31536000 is not.  i would only set a timeout, or any kind of wait or interval value, to such a high value to play a practical joke on someone.

second, and finally, if: “this variable specifies the timeout in seconds for attempts to acquire metadata locks,” then why isn’t it called metadata_lock_wait_timeout?

in conclusion: be careful when upgrading to mysql 5.5 because the solstices may pass before your dll statement completes.




MySQL

Published at DZone with permission of Peter Zaitsev, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • How to Develop a Portrait Retouching Function
  • Why Every Fintech Company Needs DevOps
  • Using the PostgreSQL Pager With MariaDB Xpand
  • PostgreSQL: Bulk Loading Data With Node.js and Sequelize

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: