peilinqian
commented
2 years ago split_db=> SHOW READWRITE_SPLITTING RULES ;
name | auto_aware_data_source_name | write_data_source_query_enabled | write_data_source_name | read_data_source_names | load_balancer_type | load_balancer_props
------+-----------------------------+---------------------------------+------------------------+------------------------+-------------------------+---------------------
ds_0 | | | write_0 | read0_0 | TRANSACTION_ROUND_ROBIN |
ds_1 | | | write_1 | read1_0 | TRANSACTION_ROUND_ROBIN |
(2 rows)rules:
- !AUTHORITY
users:
- root@%:root
- sharding@:sharding
provider:
type: ALL_PERMITTED
- !TRANSACTION
defaultType: XA
providerType: Atomikos
schemaName: split_db
dataSources:
write_0:
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 260
minPoolSize: 1
password: Test@123
url: jdbc:opengauss://10.29.180.204:15000/tpccdb?batchMode=on
username: tpccuser
read0_0:
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 260
minPoolSize: 1
password: Test@123
url: jdbc:opengauss://10.28.13.92:15000/tpccdb?batchMode=on
username: tpccuser
read0_1:
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 260
minPoolSize: 1
password: Test@123
url: jdbc:opengauss://7.212.123.28:15000/tpccdb?batchMode=on
username: tpccuser
write_1:
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 260
minPoolSize: 1
password: Test@123
url: jdbc:opengauss://10.29.180.204:16000/tpccdb?batchMode=on
username: tpccuser
read1_0:
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 260
minPoolSize: 1
password: Huawei@123
url: jdbc:opengauss://10.28.13.92:16000/tpccdb?batchMode=on
username: tpccuser
read1_1:
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 260
minPoolSize: 1
password: Test@123
url: jdbc:opengauss://7.212.123.28:16000/tpccdb?batchMode=on
username: tpccuser
rules:
- !SHARDING
tables:
t_single:
actualDataNodes: ds_0.t_single
t_single_view:
actualDataNodes: ds_0.t_single_view
t_single_view_new:
actualDataNodes: ds_0.t_single_view_new
t_ssdb_tb:
actualDataNodes: ds_${0..1}.t_ssdb_tb_${0..1}
databaseStrategy:
standard:
shardingAlgorithmName: ds_database_inline
shardingColumn: id
tableStrategy:
standard:
shardingColumn: c_id
shardingAlgorithmName: ts_t_ssdb_tb_inline
t_ssdb_tb_view:
actualDataNodes: ds_${0..1}.t_ssdb_tb_view_${0..1}
databaseStrategy:
standard:
shardingAlgorithmName: ds_database_inline
shardingColumn: id
tableStrategy:
standard:
shardingColumn: c_id
shardingAlgorithmName: ts_t_ssdb_tb_view_inline
t_ssdb:
actualDataNodes: ds_${0..1}.t_ssdb
databaseStrategy:
standard:
shardingAlgorithmName: ds_database_inline
shardingColumn: id
t_ssdb_view:
actualDataNodes: ds_${0..1}.t_ssdb_view
databaseStrategy:
standard:
shardingAlgorithmName: ds_database_inline
shardingColumn: id
t_ssdb_tbo:
actualDataNodes: ds_${0..1}.t_ssdb_tbo_${0..1}
databaseStrategy:
standard:
shardingAlgorithmName: ds_database_inline
shardingColumn: id
tableStrategy:
standard:
shardingColumn: c_id
shardingAlgorithmName: ts_t_ssdb_tbo_inline
broadcastTables:
- t_broadcast
- t_broadcast_view
bindingTables:
- t_ssdb_tb, t_ssdb_tbo, t_ssdb_tb_view
defaultTableStrategy:
none:
defaultDatabaseStrategy:
none:
shardingAlgorithms:
ds_database_inline:
type: INLINE
props:
algorithm-expression: ds_${id % 2}
allow-range-query-with-inline-sharding: true
ts_t_ssdb_tb_inline:
type: INLINE
props:
algorithm-expression: t_ssdb_tb_${c_id % 2}
allow-range-query-with-inline-sharding: true
ts_t_ssdb_tbo_inline:
type: INLINE
props:
algorithm-expression: t_ssdb_tbo_${c_id % 2}
allow-range-query-with-inline-sharding: true
ts_t_ssdb_tb_view_inline:
type: INLINE
props:
algorithm-expression: t_ssdb_tb_view_${c_id % 2}
allow-range-query-with-inline-sharding: true
- !READWRITE_SPLITTING
dataSources:
ds_0:
staticStrategy:
writeDataSourceName: write_0
readDataSourceNames:
- read0_0
- read0_1
loadBalancerName: roundRobin
ds_1:
staticStrategy:
writeDataSourceName: write_1
readDataSourceNames:
- read1_0
- read1_1
loadBalancerName: roundRobin
loadBalancers:
roundRobin:
type: TRANSACTION_ROUND_ROBIN
wsm12138
FlyingZC
Bug Report
For English only, other languages will not accept.
Before report a bug, make sure you have:
Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Which version of ShardingSphere did you use?
we find java version: java8, full_version=1.8.0_342, full_path=/home/peilq_sharding/bisheng-jdk1.8.0_342//bin/java ShardingSphere-5.2.1-SNAPSHOT Commit ID: dirty-4114e7ee4cbe5923c2b403a3e86d1f23355cadf3 Commit Message: Fix parse exception when execute insert statement with negative value (#21197) Branch: 4114e7ee4cbe5923c2b403a3e86d1f23355cadf3 Build time: 2022-09-27T16:37:07+0800
we find java version: java8, full_version=1.8.0_282, full_path=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.282.b08-1.el7_9.x86_64/bin/java ShardingSphere-5.2.1-SNAPSHOT Commit ID: dirty-bcde6f374c4a3a025173fbc9f6d0e66ed686a042 Commit Message: Fix fetch forward all error in openGauss(#21421) (#21471) Branch: bcde6f374c4a3a025173fbc9f6d0e66ed686a042 Build time: 2022-10-11T19:13:56+0800
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
Expected behavior
In READWRITE_SPLITTING mode，transaction commit is normal
Actual behavior
READWRITE_SPLITTING DB
Reason analyze (If you can)
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
Example codes for reproduce this issue (such as a github link).