Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Storage units [ds_0] do not exist in database database_name. #29323

Open
wnose opened this issue Dec 8, 2023 · 2 comments
Open

Storage units [ds_0] do not exist in database database_name. #29323

wnose opened this issue Dec 8, 2023 · 2 comments
Assignees

Comments

@wnose
Copy link

wnose commented Dec 8, 2023

IMPORT DATABASE CONFIGURATION FROM FILE "/opt/shardingsphere-proxy/conf/config-xxx.yaml"; 

I have same error. [44000][19001] Storage units [ds_0] do not exist in database database_name.

version 5.7.21-log-ShardingSphere-Proxy 5.4.1.
docker image apache/shardingsphere-proxy

databaseName: database_name

dataSources:
 ds_0:
   url: jdbc:mysql://127.0.0.1:3306/db?useUnicode=true&characterEncoding=utf-8&allowMultiQueries=true&rewriteBatchedStatements=true&serverTimezone=Asia/Shanghai&useSSL=false&zeroDateTimeBehavior=convertToNull      
   username: root
   password: 123456
   connectionTimeoutMilliseconds: 30000
   idleTimeoutMilliseconds: 60000
   maxLifetimeMilliseconds: 1800000
   maxPoolSize: 50
   minPoolSize: 1

rules:
- !SINGLE
  tables:
    - ds_0.*
  defaultDataSource: ds_0
- !SHARDING
 tables:
   lingxing_amz_order_list:
     actualDataNodes: ds_0.lingxing_amz_order_list_${0..2}
     tableStrategy:
       standard:
         shardingColumn: amazon_order_id
         shardingAlgorithmName: order_hash_mod
     keyGenerateStrategy:
        column: id
        keyGeneratorName: snowflake
     auditStrategy:
       auditorNames:
         - sharding_key_required_auditor
       allowHintDisable: true
   lingxing_amz_order_list_item:
     actualDataNodes: ds_0.lingxing_amz_order_list_item_${0..2}
     tableStrategy:
       standard:
         shardingColumn: amazon_order_id
         shardingAlgorithmName: order_hash_mod
     keyGenerateStrategy:
        column: id
        keyGeneratorName: snowflake
     auditStrategy:
       auditorNames:
         - sharding_key_required_auditor
       allowHintDisable: true
   lingxing_amz_order_detail_item:
     actualDataNodes: ds_0.lingxing_amz_order_detail_item_${0..2}
     tableStrategy:
       standard:
         shardingColumn: amazon_order_id
         shardingAlgorithmName: order_hash_mod
     keyGenerateStrategy:
        column: id
        keyGeneratorName: snowflake
     auditStrategy:
       auditorNames:
         - sharding_key_required_auditor
       allowHintDisable: true
 bindingTables:
   - lingxing_amz_order_list,lingxing_amz_order_list_item,lingxing_amz_order_detail_item
 shardingAlgorithms:
   order_hash_mod:
     type: HASH_MOD
     props:
       sharding-count: 128
 keyGenerators:
   snowflake:
     type: SNOWFLAKE
 auditors:
   sharding_key_required_auditor:
     type: DML_SHARDING_CONDITIONS

Originally posted by @wnose in #23576 (comment)

@Pace2Car
Copy link
Contributor

link to #29574

@Pace2Car
Copy link
Contributor

Pace2Car commented Jan 5, 2024

Thanks for your feedback, this is an occasional problem of metadata refresh and will be dealt with centrally.

@github-actions github-actions bot added the stale label Feb 4, 2024
@terrymanu terrymanu removed the stale label Jul 7, 2024
@apache apache deleted a comment from github-actions bot Jul 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants