on duty which violates the requirement that at least one doctor should be on call. The following diagram (quoted from Designing Data-Intensive Applications) illustrates what actually happens. 503 Figure UPDATE write conflict error • Error 8022: Error: KV error safe to retry: transaction commit failed er- ror. • Error 8028: Information schema is changed during the execution of �→ the statement: Table TiFlash Write Node 16 cores+ 32 GB+ SSD, 200 GB+ Gigabit Eth- er- net 1 TiFlash Com- pute Node 16 cores+ 32 GB+ SSD, 100 GB+ Gigabit Eth- er- net 0 (see the fol- low- ing note) 5.1.7.2 Production environment

Slow query log Y Y Y Y Y Y Y Y Y Y Y TiUP de- ploy- ment Y Y Y Y Y Y Y Y Y Y Y Kubernetes op- er- a- tor Y Y Y Y Y Y Y Y Y Y Y 75 Management, ob- serv- abil- ity, and tools 8.3 8.2 8.1 7.5 7.1 on duty which violates the requirement that at least one doctor should be on call. The following diagram (quoted from Designing Data-Intensive Applications) illustrates what actually happens. 506 Figure UPDATE write conflict error • Error 8022: Error: KV error safe to retry: transaction commit failed er- ror. • Error 8028: Information schema is changed during the execution of �→ the statement: Table

Slow query log Y Y Y Y Y Y Y Y Y Y Y Y TiUP de- ploy- ment Y Y Y Y Y Y Y Y Y Y Y Y Kubernetes op- er- a- tor Y Y Y Y Y Y Y Y Y Y Y Y Built- in phys- i- cal backup Y Y Y Y Y Y Y Y Y Y Y Y Global Kill on duty which violates the requirement that at least one doctor should be on call. The following diagram (quoted from Designing Data-Intensive Applications) illustrates what actually happens. 592 Figure UPDATE write conflict error • Error 8022: Error: KV error safe to retry: transaction commit failed er- ror. • Error 8028: Information schema is changed during the execution of �→ the statement: Table

Slow query log Y Y Y Y Y Y Y Y Y Y Y Y TiUP de- ploy- ment Y Y Y Y Y Y Y Y Y Y Y Y Kubernetes op- er- a- tor Y Y Y Y Y Y Y Y Y Y Y Y Built- in phys- i- cal backup Y Y Y Y Y Y Y Y Y Y Y Y Global Kill on duty which violates the requirement that at least one doctor should be on call. The following diagram (quoted from Designing Data-Intensive Applications) illustrates what actually happens. 587 Figure UPDATE write conflict error • Error 8022: Error: KV error safe to retry: transaction commit failed er- ror. • Error 8028: Information schema is changed during the execution of �→ the statement: Table

on duty which violates the requirement that at least one doctor should be on call. The following diagram (quoted from Designing Data-Intensive Applications) illustrates what actually happens. 503 Figure UPDATE write conflict error • Error 8022: Error: KV error safe to retry: transaction commit failed er- ror. • Error 8028: Information schema is changed during the execution of �→ the statement: Table TiFlash Write Node 16 cores+ 32 GB+ SSD, 200 GB+ Gigabit Eth- er- net 1 TiFlash Com- pute Node 16 cores+ 32 GB+ SSD, 100 GB+ Gigabit Eth- er- net 0 (see the fol- low- ing note) 5.1.7.2 Production environment

the diagram interacts with other systems and how users relate to it. More information about how to interpret this diagram can be found in the C4 model documentation about the System Context diagram. 312 Container This level is zooming in to conda on a system level, which was in the center of the Level 1 diagram, to show the high- level shape of the software architecture of and the various responsibilities in in the C4 model documentation about the Container diagram. Channels The following diagram focuses on the channels container from the level 1 diagram. 314 Chapter 4. Contributors welcome conda, Release

the diagram interacts with other systems and how users relate to it. More information about how to interpret this diagram can be found in the C4 model documentation about the System Context diagram. 316 Container This level is zooming in to conda on a system level, which was in the center of the Level 1 diagram, to show the high- level shape of the software architecture of and the various responsibilities in in the C4 model documentation about the Container diagram. Channels The following diagram focuses on the channels container from the level 1 diagram. 318 Chapter 4. Contributors welcome conda, Release

the diagram interacts with other systems and how users relate to it. More information about how to interpret this diagram can be found in the C4 model documentation about the System Context diagram. 316 Container This level is zooming in to conda on a system level, which was in the center of the Level 1 diagram, to show the high- level shape of the software architecture of and the various responsibilities in in the C4 model documentation about the Container diagram. Channels The following diagram focuses on the channels container from the level 1 diagram. 318 Chapter 4. Contributors welcome conda, Release

the diagram interacts with other systems and how users relate to it. More information about how to interpret this diagram can be found in the C4 model documentation about the System Context diagram. 320 Container This level is zooming in to conda on a system level, which was in the center of the Level 1 diagram, to show the high- level shape of the software architecture of and the various responsibilities in in the C4 model documentation about the Container diagram. Channels The following diagram focuses on the channels container from the level 1 diagram. 322 Chapter 4. Contributors welcome conda, Release

the diagram interacts with other systems and how users relate to it. More information about how to interpret this diagram can be found in the C4 model documentation about the System Context diagram. 344 Container This level is zooming in to conda on a system level, which was in the center of the Level 1 diagram, to show the high- level shape of the software architecture of and the various responsibilities in in the C4 model documentation about the Container diagram. Channels The following diagram focuses on the channels container from the level 1 diagram. 346 Chapter 4. Contributors welcome conda, Release