🐞 bug: When PITR backup, --dn-threads-num is set to 10, and the actual dn node executes “--threads=1” - Githubissues

apache / shardingsphere-on-cloud

A collection of tools and best practices to take ShardingSphere into the cloud

Apache License 2.0

83 stars 28 forks source link

🐞 bug: When PITR backup, --dn-threads-num is set to 10, and the actual dn node executes “--threads=1” #455

Closed peilinqian closed 9 months ago

peilinqian commented 9 months ago

Environment

Contents of your values.yaml file,if your helm deployment process goes wrong.
Contents of your CRD resource file. Include proxy.shardingsphere.apache.org/v1alpha1 and proxyconfig.shardingsphere.apache.org/v1alpha1
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version

Issue description

Which phase is not functioning properly, is it the installation phase or the apply CRD phase ?

When PITR backup, --dn-threads-num is set to 10, and the actual dn node executes “--threads=1”

Error log

Including ShardingSphere-Proxy error log and ShardingSphere-Operator error log

Expected result

When PITR backup, --dn-threads-num is set to 10, and the actual dn node executes “--threads=10”