Automatic Data rebalancing by adding new data node

[jainanuj07]

I have set up ShardingSphere-Proxy with two data sources and defined a sharding rule using the MOD function on the ID column. After adding a new data source, I noticed that new data is being distributed across the updated nodes, but the existing data remains on the original instances.

Does ShardingSphere support automatic rebalancing when a new data source is added?

[jainanuj07]

@terrymanu can you pls help.

[terrymanu]

What is the version and config

[jainanuj07]

Version : 5.5.2

data:
config-sharding.yaml: |
databaseName: api-beta-test
dataSources:
ds_0:
url:
username:
password:
ds_1:
url:
username:
password:
rules:
- !SHARDING
tables:
payments:
actualDataNodes: ds_0.payments_0, ds_1.payments_1
tableStrategy:
standard:
shardingColumn: merchant_id
shardingAlgorithmName: payments_table_algorithm
keyGenerateStrategy:
column: id
keyGeneratorName: snowflake
defaultDatabaseStrategy:
standard:
shardingColumn: merchant_id
shardingAlgorithmName: database_sharding_algorithm
defaultTableStrategy:
none: {}
shardingAlgorithms:
database_sharding_algorithm:
type: INLINE
props:
algorithm-expression: ds_${Math.abs(merchant_id.hashCode()) % 2 }
payments_table_algorithm:
type: INLINE
props:
algorithm-expression: payments_${Math.abs(merchant_id.hashCode()) % 2}
keyGenerators:
snowflake:
type: SNOWFLAKE

This is my current config and now I want to add one more datasource and shard the data for some merchants to new data source. So I will add and change the hash mod algo. This is my new Config.

data:
config-sharding.yaml: |
databaseName: api-beta-test
dataSources:
ds_0:
url:
username:
password:
ds_1:
url:
username:
password:
ds_2:
url:
username:
password:
rules:
- !SHARDING
tables:
payments:
actualDataNodes: ds_0.payments_0, ds_1.payments_1,ds_2.payments_2
tableStrategy:
standard:
shardingColumn: merchant_id
shardingAlgorithmName: payments_table_algorithm
keyGenerateStrategy:
column: id
keyGeneratorName: snowflake
defaultDatabaseStrategy:
standard:
shardingColumn: merchant_id
shardingAlgorithmName: database_sharding_algorithm
defaultTableStrategy:
none: {}
shardingAlgorithms:
database_sharding_algorithm:
type: INLINE
props:
algorithm-expression: ds_${Math.abs(merchant_id.hashCode()) % 3 }
payments_table_algorithm:
type: INLINE
props:
algorithm-expression: payments_${Math.abs(merchant_id.hashCode()) % 3}
keyGenerators:
snowflake:
type: SNOWFLAKE

[terrymanu]

The SphereEx enterprise version include this feature:
https://www.sphere-ex.cn/comparison/

ShardingSphere currently remains focused on managing database traffic and has no immediate plans to expand its product feature scope.