The Vitess 5.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Production Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Production testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . all YouTube database traffic since 2011, and has now been adopted by many enterprises for their production needs. Concepts description: Learn core Vitess concepts and terminology Cell description: Data0 码力 | 206 页 | 875.06 KB | 1 年前3
The Vitess 6.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Production Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Production testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . all YouTube database traffic since 2011, and has now been adopted by many enterprises for their production needs. 9 Concepts description: Learn core Vitess concepts and terminology Cell description:0 码力 | 210 页 | 846.79 KB | 1 年前3
The Vitess 7.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Production Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Production testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Similarly, tables that are updated at a more frequent rate could increase the move time. Impact to Production Traffic Internally, a MoveTables operation is comprised of both a table copy and a subscription0 码力 | 254 页 | 949.63 KB | 1 年前3
The Vitess 8.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Production Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Production testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Similarly, tables that are updated at a more frequent rate could increase the move time. Impact to Production Traffic Internally, a MoveTables operation is comprised of both a table copy and a subscription0 码力 | 331 页 | 1.35 MB | 1 年前3
The Vitess 9.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Running in Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Similarly, tables that are updated at a more frequent rate could increase the move time. Impact to Production Traffic Internally, a MoveTables operation is comprised of both a table copy and a subscription move process, data is copied from replicas instead of the master server. This helps ensure minimal production traffic impact. During the SwitchWrites phase of the MoveTables operation, Vitess may be briefly0 码力 | 417 页 | 2.96 MB | 1 年前3
The Vitess 11.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Running in Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Similarly, tables that are updated at a more frequent rate could increase the move time. 21 Impact to Production Traffic Internally, a MoveTables operation is comprised of both a table copy and a subscription move process, data is copied from replicas instead of the master server. This helps ensure minimal production traffic impact. During the SwitchWrites phase of the MoveTables operation, Vitess may be briefly0 码力 | 481 页 | 3.14 MB | 1 年前3
The Vitess 10.0 Documentation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Running in Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Similarly, tables that are updated at a more frequent rate could increase the move time. Impact to Production Traffic Internally, a MoveTables operation is comprised of both a table copy and a subscription move process, data is copied from replicas instead of the master server. This helps ensure minimal production traffic impact. During the SwitchWrites phase of the MoveTables operation, Vitess may be briefly0 码力 | 455 页 | 3.07 MB | 1 年前3
The Vitess 12.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Character set support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 16 Running in Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Similarly, tables that are updated at a more frequent rate could increase the move time. Impact to Production Traffic Internally, a MoveTables operation is comprised of both a table copy and a subscription0 码力 | 534 页 | 3.32 MB | 1 年前3
Vitess security auditmodelling should be seen as an ongoing effort. Future security disclosures to the Vitess security team are opportunities to evaluate the threat model of the affected components. Most compromises of VTAdmin MySQL Protocol To implement MySQL handshake 2 Vindexes Non-cryptographic hash 3 Evalengine To support MySQL built-in functions 4 Tmutils Non-cryptographic hash 5 S3 Backup Storage Non-cryptographic only if users choose to expose them, to prevent accidentally revealing sensitive information in a production deployment. https://github.com/vitessio/vitess/blob/137cf9daf41112a553f617c66a56fd8b06fad20b/go/0 码力 | 41 页 | 1.10 MB | 1 年前3
Pentest-Report Vitess 02.2019miscellaneous findings. In terms of resources, the test was completed by six members of the Cure53 team who worked within a time budget of eighteen days. The testers are considered very experienced assessment, a CNCF-typical setup was requested by the testers and provided by the development team. Besides furnishing Cure53 with a Kubernetes-based cluster, locally installed systems were also used interfaces and the system architecture, supported also by additional exchange with the development team, revealed a rather limited attack surface. This observation was later confirmed as the subsequent0 码力 | 9 页 | 155.02 KB | 1 年前3
共 12 条
- 1
- 2













