. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 Rolling Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . following info from a table: • Field info • PK columns • Table comments VTTablet also gathered table statistics from information schema. However, we don’t think anyone is using them. So, it may be better to It is too expensive to get real-time row counts of tables, using _count(*)_, say. So we use the statistics available in the information_schema to approximate copy progress. This data can be significantly

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Rolling Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . following info from a table: • Field info • PK columns • Table comments VTTablet also gathered table statistics from information schema. However, we don’t think anyone is using them. So, it may be better to It is too expensive to get real-time row counts of tables, using _count(*)_, say. So we use the statistics available in the information_schema to approximate copy progress. This data can be significantly

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 Rolling Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . following info from a table: • Field info • PK columns • Table comments VTTablet also gathered table statistics from information schema. However, we don’t think anyone is using them. So, it may be better to It is too expensive to get real-time row counts of tables, using _count(*)_, say. So we use the statistics available in the information_schema to approximate copy progress. This data can be significantly

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 19 Rolling Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . following info from a table: • Field info • PK columns • Table comments VTTablet also gathered table statistics from information schema. However, we don’t think anyone is using them. So, it may be better to It is too expensive to get real-time row counts of tables, using _count(*)_, say. So we use the statistics available in the information_schema to approximate copy progress. This data can be significantly

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Rolling Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the upgrade did not introduce a regression. Eventually, you can upgrade the remaining instances. Rolling Upgrades We recommend to automate the upgrade process with a configuration management software. software. Therefore, we invite open-source users to contribute such templates. Any upgrade should be a rolling release i.e. usually one tablet at a time within a shard. This ensures that the remaining tablets

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Rolling Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the upgrade did not introduce a regression. Eventually, you can upgrade the remaining instances. Rolling Upgrades We recommend to automate the upgrade process with a configuration management software. software. Therefore, we invite open-source users to contribute such templates. Any upgrade should be a rolling release i.e. usually one tablet at a time within a shard. This ensures that the remaining tablets

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Rolling Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the upgrade did not introduce a regression. Eventually, you can upgrade the remaining instances. Rolling Upgrades We recommend to automate the upgrade process with a configuration management software. software. Therefore, we invite open-source users to contribute such templates. Any upgrade should be a rolling release i.e. usually one tablet at a time within a shard. This ensures that the remaining tablets

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Rolling Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the upgrade did not introduce a regression. Eventually, you can upgrade the remaining instances. Rolling Upgrades We recommend to automate the upgrade process with a configuration management software. software. Therefore, we invite open-source users to contribute such templates. Any upgrade should be a rolling release i.e. usually one tablet at a time within a shard. This ensures that the remaining tablets