Vitess can run as a Kubernetes-aware cloud native distributed database. 35 Kubernetes handles scheduling onto nodes in a compute cluster, actively manages workloads on those nodes, and groups containers another system. • Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are alpha, and can be improved. Here is the list of possible limitations/improvements: • Proactive scheduling: Upcoming messages can be proactively scheduled for timely delivery instead of waiting for the

and Vitess can run as a Kubernetes-aware cloud native distributed database. Kubernetes handles scheduling onto nodes in a compute cluster, actively manages workloads on those nodes, and groups containers another system. • Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are alpha, and can be improved. Here is the list of possible limitations/improvements: • Proactive scheduling: Upcoming messages can be proactively scheduled for timely delivery instead of waiting for the

and Vitess can run as a Kubernetes-aware cloud native distributed database. Kubernetes handles scheduling onto nodes in a compute cluster, actively manages workloads on those nodes, and groups containers system. 46 • Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are alpha, and can be improved. Here is the list of possible limitations/improvements: • Proactive scheduling: Upcoming messages can be proactively scheduled for timely delivery instead of waiting for the

and Vitess can run as a Kubernetes-aware cloud native distributed database. Kubernetes handles scheduling onto nodes in a compute cluster, actively manages workloads on those nodes, and groups containers another system. • Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are alpha, and can be improved. Here is the list of possible limitations/improvements: • Proactive scheduling: Upcoming messages can be proactively scheduled for timely delivery instead of waiting for the

etc. This document explain the general logic behind onlineddl.Executor and, in particular, the scheduling aspect. OnlineDDL & VTTablet state manager onlineddl.Executor runs on PRIMARY tablets. It Opens and Vitess can run as a Kubernetes-aware cloud native distributed database. Kubernetes handles scheduling onto nodes in a compute cluster, actively manages workloads on those nodes, and groups containers another system. • Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are

and Vitess can run as a Kubernetes-aware cloud native distributed database. Kubernetes handles scheduling onto nodes in a compute cluster, actively manages workloads on those nodes, and groups containers another system. • Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are alpha, and can be improved. Here is the list of possible limitations/improvements: • Proactive scheduling: Upcoming messages can be proactively scheduled for timely delivery instead of waiting for the

Kubernetes-aware cloud native distributed database. 93 Figure 2: Architecture Diagram Kubernetes handles scheduling onto nodes in a compute cluster, actively manages workloads on those nodes, and groups containers another system. • Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are alpha, and can be improved. Here is the list of possible limitations/improvements: • Proactive scheduling: Upcoming messages can be proactively scheduled for timely delivery instead of waiting for the

and Vitess can run as a Kubernetes-aware cloud native distributed database. Kubernetes handles scheduling onto nodes in a compute cluster, actively manages workloads on those nodes, and groups containers another system. • Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. 98 • Accumulating work that could be done during off-peak hours. Messages alpha, and can be improved. Here is the list of possible limitations/improvements: • Proactive scheduling: Upcoming messages can be proactively scheduled for timely delivery instead of waiting for the