document, v5.1.2 4.2.3 Goal The goal of Apache ShardingSphere management module is to realize the integrated management ability from database to computing node, and provide control ability for components Built‐in transaction managers have already been able to provide services through jar packages. Integrated with Apache ShardingSphere, it can guarantee the high con‐ sistency in cross‐database transactions metrics and logging features. Enable the plugin in agent to collect data and send data to the integrated 3rd APM system. 4.10. Observability 66 Apache ShardingSphere document, v5.1.2 APM APM is the

single node. 3.6.3 Goal The goal of Apache ShardingSphere management module is to realize the integrated management abil‐ ity from database to computing node, and provide control ability for components storage tier component processes. These can either be physical ma‐ chines, virtual machines, or containers, etc. Cluster Multiple nodes that are assembled together to provide a specified service. 3.7 The resources limits for the ZooKeeper containers {} governance.zookeeper.r es- ources.requests.memory The requested memory for the ZooKeeper containers ˋ 256Mi` governance.zookeepe r. resources

single node. 8.5.3 Goal The goal of Apache ShardingSphere management module is to realize the integrated management abil‐ ity from database to computing node, and provide control ability for components storage tier component processes. These can either be physical ma‐ chines, virtual machines, or containers, etc. Cluster Multiple nodes that are assembled together to provide a specified service. Source limits The resources limits for the ZooKeeper containers {} governance.zookeeper.re sources.requests.memory The requested memory for the ZooKeeper containers 256Mi governance.zookeeper . resources

single node. 3.6.3 Goal The goal of Apache ShardingSphere management module is to realize the integrated management abil‐ ity from database to computing node, and provide control ability for components storage tier component processes. These can either be physical ma‐ chines, virtual machines, or containers, etc. Cluster Multiple nodes that are assembled together to provide a specified service. 3.7 The resources limits for the ZooKeeper containers {} governance.zookeeper.r es- ources.requests.memory The requested memory for the ZooKeeper containers ˋ 256Mi` governance.zookeepe r. resources

single node. 8.5.3 Goal The goal of Apache ShardingSphere management module is to realize the integrated management abil‐ ity from database to computing node, and provide control ability for components storage tier component processes. These can either be physical ma‐ chines, virtual machines, or containers, etc. Cluster Multiple nodes that are assembled together to provide a specified service. Source limits The resources limits for the ZooKeeper containers {} governance.zookeeper.re sources.requests.memory The requested memory for the ZooKeeper containers 256Mi governance.zookeeper . resources

single node. 4.2.3 Goal The goal of Apache ShardingSphere management module is to realize the integrated management ability from database to computing node, and provide control ability for components Built‐in transaction managers have already been able to provide services through jar packages. Integrated with Apache ShardingSphere, it can guarantee the high con‐ sistency in cross‐database transactions metrics and logging features. Enable the plugin in agent to collect data and send data to the integrated 3rd APM system. APM APM is the abbreviation for application performance monitoring. It works

The resources limits for the ZooKeeper containers ## @param governance.zookeeper.resources.requests.memory The requested memory for the ZooKeeper containers ## @param governance.zookeeper.resources resources.requests.cpu The requested cpu for the ZooKeeper containers ## resources: limits: {} requests: memory: 256Mi cpu: 250m ## @section Compute-Node parameters ## compute: ## @section Compute-Node ShardingSphere-Proxy 140 Apache ShardingSphere document ## ref: https://kubernetes.io/docs/concepts/containers/images/ ## @param compute.image.repository Image name of ShardingSphere-Proxy. ## @param compute

The resources limits for the ZooKeeper containers ## @param governance.zookeeper.resources.requests.memory The requested memory for the ZooKeeper containers ## @param governance.zookeeper.resources resources.requests.cpu The requested cpu for the ZooKeeper containers ## resources: limits: {} requests: memory: 256Mi cpu: 250m ## @section Compute-Node parameters ## compute: ## @section Compute-Node ShardingSphere-Proxy 134 Apache ShardingSphere document ## ref: https://kubernetes.io/docs/concepts/containers/images/ ## @param compute.image.repository Image name of ShardingSphere-Proxy. ## @param compute

The resources limits for the ZooKeeper containers ## @param governance.zookeeper.resources.requests.memory The requested memory for the ZooKeeper containers ## @param governance.zookeeper.resources resources.requests.cpu The requested cpu for the ZooKeeper containers ## resources: limits: {} requests: memory: 256Mi cpu: 250m ## @section Compute-Node parameters ## compute: ## @section Compute-Node ShardingSphere-Proxy 175 Apache ShardingSphere document, v5.2.0 ## ref: https://kubernetes.io/docs/concepts/containers/images/ ## @param compute.image.repository Image name of ShardingSphere-Proxy. ## @param compute

The resources limits for the ZooKeeper containers ## @param governance.zookeeper.resources.requests.memory The requested memory for the ZooKeeper containers ## @param governance.zookeeper.resources resources.requests.cpu The requested cpu for the ZooKeeper containers ## resources: limits: {} requests: memory: 256Mi cpu: 250m ## @section Compute-Node parameters ## compute: ## @section Compute-Node ShardingSphere-Proxy 158 Apache ShardingSphere document ## ref: https://kubernetes.io/docs/concepts/containers/images/ ## @param compute.image.repository Image name of ShardingSphere-Proxy. ## @param compute