Edit this pageDocumentationFAQTroubleshootingCommon ErrorsWhat can I do if I see a CPU increase after upgrading Vitess?What can I do if I see a CPU increase after upgrading Vitess? Documentation Documentationv24.0 (Stable) Overview Get Started Concepts User Guides Reference v25.0 (Development) Overview Get Started Concepts User Guides Reference Troubleshoot Elevated query latency on primary Primary starts up read-only Vitess sees the wrong tablet as primary FAQ Getting Started Overview Migrating Operating Vitess Troubleshooting Sharding Advanced Configuration Learning Resources v23.0 (Stable) Overview Get Started Concepts User Guides Reference Contribute GitHub Workflow Sample First Issue Coding Standards PR Naming Conventions Build on Ubuntu/Debian Build on macOS Build on CentOS Parser and AST Roadmap Design Docs Query Serving Online DDL VReplication VTTablet Miscellaneous Archives Older Version Docs v22.0 (Archived) v21.0 (Archived) v20.0 (Archived) v19.0 (Archived) v18.0 (Archived) v17.0 (Archived) v16.0 (Archived) v15.0 (Archived) v14.0 (Archived) v13.0 (Archived) v12.0 (Archived) v11.0 (Archived)<< Prev Next >>If you are running Vitess 7.0 or above, we introduced the schema tracker, which could be running on the VTTablets now. You can disable it in order to prevent that reporting.You will need to add track_schema_versions as false in the VTTablet.<< Prev Next >>