XA transaction adopts the concepts including AP(application program), YM(transaction manager) and RM(resource manager) to ensure the strong consistency of distributed transactions. Those concepts are abstracted for running compute or storage tier component processes. These can either be physical ma‐ chines, virtual machines, or containers, etc. Cluster Multiple nodes that are assembled together to provide a specified document, v5.2.0 Procedure 1. Configure the transaction manager 2. Use distributed transactions Sample Configure the transaction manager

XA transaction adopts the concepts including AP(application program), TM(transaction manager) and RM(resource manager) to ensure the strong consistency of distributed transactions. Those concepts are abstracted for running compute or storage tier component processes. These can either be physical ma‐ chines, virtual machines, or containers, etc. Cluster Multiple nodes that are assembled together to provide a specified version} Procedure 1. Configure the transaction manager 2. Use distributed transactions Sample Configure the transaction manager

each data node to manage their own transactions on the premise that any distributed trans‐ action manager is not on. They do not have any coordination and communication ability, or know other data nodes Model defined by X/OPEN, in which created AP (Application Pro‐ gram), TM (Transaction Manager) and RM (Resource Manager) can guarantee a high transaction con‐ sistency. TM and RM use XA protocol for bidirectional XA driver provided by database manufacturers and TransactionManager is provided by trans‐ action manager manufacturers. Traditional transaction managers need to be bound with application server, which

each data node to manage their own transactions on the premise that any distributed trans‐ action manager is not on. They do not have any coordination and communication ability, or know other data nodes Model defined by X/OPEN, in which created AP (Application Pro‐ gram), TM (Transaction Manager) and RM (Resource Manager) can guarantee a high transaction con‐ sistency. TM and RM use XA protocol for bidirectional XA driver provided by database manufacturers and TransactionManager is provided by trans‐ action manager manufacturers. Traditional transaction managers need to be bound with application server, which

each data node to manage their own transactions on the premise that any distributed trans‐ action manager is not on. They do not have any coordination and communication ability, or know other data nodes Model defined by X/OPEN, in which created AP (Application Pro‐ gram), TM (Transaction Manager) and RM (Resource Manager) can guarantee a high transaction con‐ sistency. TM and RM use XA protocol for bidirectional XA driver provided by database manufacturers and TransactionManager is provided by trans‐ action manager manufacturers. Traditional transaction managers need to be bound with application server, which

each data node to manage their own transactions on the premise that any distributed trans‐ action manager is not on. They do not have any coordination and communication ability, or know other data nodes Model defined by X/OPEN, in which created AP (Application Pro‐ gram), TM (Transaction Manager) and RM (Resource Manager) can guarantee a high transaction con‐ sistency. TM and RM use XA protocol for bidirectional XA driver provided by database manufacturers and TransactionManager is provided by trans‐ action manager manufacturers. Traditional transaction managers need to be bound with application server, which

XA transaction adopts the concepts including AP(application program), TM(transaction manager) and RM(resource manager) to ensure the strong consistency of distributed transactions. Those concepts are abstracted In MySQL8, you need to grant the user XA_RECOVER_ADMIN privileges, otherwise, the XA transaction manager will report an error when executing the XA RECOVER statement. 8.3 Readwrite-splitting 8.3.1 Background for running compute or storage tier component processes. These can either be physical ma‐ chines, virtual machines, or containers, etc. Cluster Multiple nodes that are assembled together to provide a specified

XA transaction adopts the concepts including AP(application program), TM(transaction manager) and RM(resource manager) to ensure the strong consistency of distributed transactions. Those concepts are abstracted In MySQL8, you need to grant the user XA_RECOVER_ADMIN privileges, otherwise, the XA transaction manager will report an error when executing the XA RECOVER statement. 8.3 Readwrite-splitting 8.3.1 Background for running compute or storage tier component processes. These can either be physical ma‐ chines, virtual machines, or containers, etc. Cluster Multiple nodes that are assembled together to provide a specified

ShardingSphere‐JDBC 的分片场景 API。 强制路由 背景信息 Apache ShardingSphere 使用 ThreadLocal 管理分片键值进行强制路由。可以通过编程的方式向 Hint‐ Manager 中添加分片值，该分片值仅在当前线程内生效。Apache ShardingSphere 还可以通过 SQL 中增 加注释的方式进行强制路由。 Hint 的主要使用场景：‐ 分片字段不存在 SQL props: xa-transaction-manager-type: Atomikos Spring Namespace: Atomikos props: xa-transaction-manager-type: Narayana Spring Namespace: Narayana

DataSource dataSource; 强制路由 简介 Apache ShardingSphere 使用 ThreadLocal 管理分片键值进行强制路由。可以通过编程的方式向 Hint‐ Manager 中添加分片值，该分片值仅在当前线程内生效。 Hint 的主要使用场景： • 分片字段不存在 SQL 和数据库表结构中，而存在于外部业务逻辑。 • 强制在主库进行某些数据操作。 4.1. 详情请参见Narayana 官方文档。 设置 XA 事务管理类型 Yaml: props: xa-transaction-manager-type: Narayana SpringBoot: spring: shardingsphere: props: xa-transaction-manager-type: Narayana Spring Namespace: Narayana 4.1. ShardingSphere-JDBC 170 Apache ShardingSphere document, v5.0.0-beta