Qumans opened a new issue, #15543:
URL: https://github.com/apache/shardingsphere/issues/15543
### Which version of ShardingSphere did you use?
5.1.0
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
### Expected behavior
Does not take up too much startup time
### Actual behavior
Loading metadata consumes a lot of time
### Reason analyze (If you can)
The amount of metadata is too large, there are about 400,000 pieces, and it
is increasing every day，v5.1.0 can only solve the immediate problem, there will
still be problems in the future
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule
configuration, when exception occur etc.
datasource:
ds-0:
driver-class-name: com.mysql.cj.jdbc.Driver
type: com.alibaba.druid.pool.DruidDataSource
url:
username:
password:
maxWait: 60000
maxActive: 1000
maxIdle: 20
initialSize: 20
removeAbandoned: true
validationQuery: SELECT 1
testOnBorrow: false
testOnReturn: false
testWhileIdle: true
names: ds-0
rules:
sharding:
tables:
prod_gray_cloth_inventory:
actualDataNodes: ds-0.table_$->{0..31}
keyGenerateStrategy:
column: id
props:
worker:
id: 100
keyGeneratorName: SNOWFLAKE
tableStrategy:
standard:
shardingAlgorithmName: inventoryalg
shardingColumn:
sharding-algorithms:
inventoryalg:
type:
props:
strategy: STANDARD
algorithmClassName:
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
[email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
