Rookie DBA Mistakes: How I Screwed Up So You Don't Have To
Many MySQL database administrators start out as software developers, sysadmins or devops engineers who are assigned to handle the databases without any formal training or mentoring. They then rely on Google to answer any questions. This can lead them to incorrect answers on sites like Stack Overflow, or in misunderstanding the official documentation due to lack of background knowledge. This talk will be about the common mistakes and misconceptions new DBAs often make in their first year managing MySQL servers. It will be based on my own blunders over the years, as well as those which I'd observed in my 3 years on the MySQL support team at Oracle. Some of the concepts covered will be: - misleading error messages - session vs global variables - how not to run out of memory - how configuration files can troll you - the meaning of the different data files, and what not to delete - why mixing MyISAM and InnoDB tables is a bad idea - SHOW SLAVE STATUS and its badly named variables - how not to set up an inconsistent replica - what happens when you skip slave errors This talk is aimed at beginner database administrators.
Gillian joined the GitHub infrastructure team in January 2016. She's worked as a DBA at such companies as Okta, PalominoDB/BlackbirdIT, Pythian and Disney, and spent 3 years on the MySQL support team at Oracle. Her home base is Vancouver, BC.