required by default, Proxy will automatically choose the authentication method according to the frontend protocol type authenticatorName: type: # Authentication method type defaultAuthenticator: # Optional for root@127.0.0.1, Proxy will automatically choose the authentication method according to the frontend protocol; ‐ Privilege provider is not specified, the default ALL_PERMITTED will be used; 9.2. to set their own custom config‐ urations according to their scenarios. Taking openGauss as the frontend protocol type as an example, its default authentication method is scram-sha-256. If the user sharding

required by default, Proxy will automatically choose the authentication method according to the frontend protocol type authenticatorName: type: # Authentication method type defaultAuthenticator: # Optional for root@127.0.0.1, Proxy will automatically choose the authentication method according to the frontend protocol; ‐ Privilege provider is not specified, the default ALL_PERMITTED will be used; Authentication to set their own custom config‐ urations according to their scenarios. Taking openGauss as the frontend protocol type as an example, its default authentication method is scram-sha-256. If the user sharding

3307 | | proxy_frontend_database_protocol_type | | | proxy_frontend_executor_size | 0 | | proxy_frontend_flush_threshold | 128 | | proxy_frontend_max_connections | 0 | | proxy_frontend_ssl_cipher | | | | proxy_frontend_ssl_enabled | false | | proxy_frontend_ssl_version | TLSv1.2,TLSv1.3 | | proxy_meta_data_collector_enabled | true | | proxy_netty_backlog | 1024 | | sql_federation_type | NONE | ShardingSphere‐Proxy： sh bin/start.sh 5. 查看 proxy 日志 logs/stdout.log，看到日志中出现： [INFO ] [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success 确认启动成功。 6. 按需配置迁移 6.1. 查询配置。 SHOW

3307 | | proxy_frontend_database_protocol_type | | | proxy_frontend_executor_size | 0 | | proxy_frontend_flush_threshold | 128 | | proxy_frontend_max_connections | 0 | | proxy_frontend_ssl_cipher | | | | proxy_frontend_ssl_enabled | false | | proxy_frontend_ssl_version | TLSv1.2,TLSv1.3 | | proxy_meta_data_collector_enabled | true | | proxy_netty_backlog | 1024 | | sql_federation_type | NONE | ShardingSphere‐Proxy： sh bin/start.sh 5. 查看 proxy 日志 logs/stdout.log，看到日志中出现： [INFO ] [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success 确认启动成功。 6. 按需配置迁移 6.1. 查询配置。 SHOW

3307 | | proxy_frontend_database_protocol_type | | | proxy_frontend_executor_size | 0 | | proxy_frontend_flush_threshold | 128 | | proxy_frontend_max_connections | 0 | | proxy_frontend_ssl_cipher | | | | proxy_frontend_ssl_enabled | false | | proxy_frontend_ssl_version | TLSv1.2,TLSv1.3 | | proxy_meta_data_collector_enabled | true | | proxy_netty_backlog | 1024 | | sql_federation_type | NONE | ShardingSphere‐Proxy： sh bin/start.sh 5. 查看 proxy 日志 logs/stdout.log，看到日志中出现： [INFO ] [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success 确认启动成功。 6. 按需配置迁移 6.1. 查询配置。 SHOW

when writing packets to the client，but if the number of client con‐ nections exceeds proxy-frontend-executor-size， especially with slow SQL, it can cause a longer delay to SQL execution and View the proxy log logs/stdout.log. If you see the following statements: [INFO ] [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success The startup will have been successful shardingsphere:shardingsphere-proxy-frontend-core, used by ShardingSphere‐Proxy to parse and adapt the protocol for accessing the database • org.apache.shardingsphere:shardingsphere-proxy-frontend-mysql, a MySQL im‐

sharding@:sharding props: max-connections-size-per-query: 10 executor-size: 128 # Infinite by default. proxy-frontend-flush-threshold: 128 # The default value is 128. # LOCAL: Proxy will run with LOCAL transaction default value is available processors count * 2. executor.size: 128 # Infinite by default. proxy.frontend.flush.threshold: 128 # The default value is 128. # LOCAL: Proxy will run with LOCAL transaction default value is available processors count * 2. executor.size: 128 # Infinite by default. proxy.frontend.flush.threshold: 128 # The default value is 128. # LOCAL: Proxy will run with LOCAL transaction

startup or updated. f a l s e f a l s e p rox y‐f ron ten d‐e xec uto r‐s ize (?) i n t Proxy frontend Netty executor size. The default value is 0, which means let Netty decide. 0 f a l s e p latency of SQL execution and block other clients if client connections are more than proxy-frontend-executor-size, especially exe‐ cuting slow SQL. O L A P f a l s e pro xy‐ fro nte nd‐ max ‐co ShardingSphere document, v5.1.1 sh bin/start.sh 6. Check proxy log logs/stdout.log: [INFO ] [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success It means proxy start up successfully

startup or updated. f a l s e t r u e p rox y‐f ron ten d‐e xec uto r‐s ize (?) i n t Proxy frontend Netty executor size. The default value is 0, which means let Netty decide. 0 f a l s e p latency of SQL execution and block other clients if client connections are more than proxy-frontend-executor-size, especially exe‐ cuting slow SQL. O L A P t r u e pro xy‐ fro nte nd‐ max ‐co ShardingSphere‐Proxy: sh bin/start.sh 7. Check proxy log logs/stdout.log: [INFO ] [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success It means proxy start up successfully

when writing packets to the client，but if the number of client connec‐ tions exceeds ˋ proxy­frontend­ executor­size`， especially with slow SQL, it can cause a longer delay to SQL execution and View the proxy log logs/stdout.log. If you see the following statements: [INFO ] [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success The startup will have been successful 6.1 DatabaseProtocolFrontendEngine Fully-qualified class name org.apache.shardingsphere.proxy.frontend.spi.DatabaseProtocolFrontendEngine Definition Protocols for ShardingSphere‐Proxy to parse and