Seata分布式事务实战 2

@SpringBootApplication
@EnableDiscoveryClient
@EnableFeignClients(basePackages = {"com.itheima.driver.feign"})
@EnableAutoDataSourceProxy
public class OrderApplication {
}

@Override
@GlobalTransactional
public OrderInfo addOrder() {
    //创建订单
        OrderInfo orderInfo = new OrderInfo("No"+((int)(Math.random()*10000)), (int)(Math.random()*100), new Date(), "深圳北站", "罗湖港", null);
        int count = orderInfoMapper.add(orderInfo);
        //修改司机信息  司机ID=1
        Driver driver = driverFeign.status("1",2);
        orderInfo.setDriver(driver);
        return orderInfo;
}

@Override
@GlobalTransactional
public OrderInfo addOrder() {
    //修改司机信息  司机ID=1
    Driver driver = driverFeign.status("1",2);
    //创建订单
    OrderInfo orderInfo = new OrderInfo("No"+((int)(Math.random()*10000)), (int)(Math.random()*100), new Date(), "深圳北站", "罗湖港", driver);
    int count = orderInfoMapper.add(orderInfo);
    System.out.println("====count="+count);
    //模拟异常
    int i = 1 / 0;
    return orderInfo;
}

有一个 TCC 拦截器，它会封装 Confirm 和 Cancel 方法作为资源（用于后面 TC 来 commit 或 rollback 操作）
封装完，它会本地缓存到 RM （缓存的是方法的描述信息），可以简单认为是放到一个 Map 里面
当 TC 想调用的时候，就可以从 Map 里找到这个方法，用反射调用就可以了
另外，RM 不光是注册分支事务（分支事务是注册到 TC 里的 GlobalSession 中的）
它还会把刚才封装的资源里的重要属性（事务ID、归属的事务组等）以资源的形式注册到 TC 中的 RpcContext
这样，TC 就知道当前全局事务都有哪些分支事务了（这都是分支事务初始化阶段做的事情）
举个例子：RpcContext里面有资源 123，但是 GlobalSession 里只有分支事务 12
于是 TC 就知道分支事务 3 的资源已经注册进来了，但是分支事务 3 还没注册进来
这时若 TM 告诉 TC 提交或回滚，那 GlobalSession 就会通过 RpcContext 找到 1 和 2 的分支事务的位置（比如该调用哪个方法）
当 RM 收到提交或回滚后，就会通过自己的本地缓存找到对应方法，最后通过反射或其他机制去调用真正的 Confirm 或 Cancel

registry {
  # file ...nacos ...eureka...redis...zk...consul...etcd3...sofa
  type = "nacos"
  nacos {
    application = "seata-server"
    serverAddr = "192.168.200.200:8848"
    group = "SEATA_GROUP"
    namespace = "1ebba5f6-49da-40cc-950b-f75c8f7d07b3"
    cluster = "default"
    username = "nacos"
    password = "nacos"
  }
}

  registry:
    type: nacos
    nacos:
      application: seata-server
      server-addr: 192.168.200.200:8848
      group : "SEATA_GROUP"
      namespace: 1ebba5f6-49da-40cc-950b-f75c8f7d07b3
      username: "nacos"
      password: "nacos"

seata:
enabled: true
application-id: ${spring.application.name}
tx-service-group: my_test_tx_group
enable-auto-data-source-proxy: true
use-jdk-proxy: false
excludes-for-auto-proxying: firstClassNameForExclude,secondClassNameForExclude
client:
 rm:
   async-commit-buffer-limit: 1000
   report-retry-count: 5
   table-meta-check-enable: false
   report-success-enable: false
   saga-branch-register-enable: false
   lock:
     retry-interval: 10
     retry-times: 30
     retry-policy-branch-rollback-on-conflict: true
 tm:
   degrade-check: false
   degrade-check-period: 2000
   degrade-check-allow-times: 10
   commit-retry-count: 5
   rollback-retry-count: 5
 undo:
   data-validation: true
   log-serialization: jackson
   log-table: undo_log
   only-care-update-columns: true
 log:
   exceptionRate: 100
service:
 vgroup-mapping:
   my_test_tx_group: default
 #grouplist:
   #default: 192.168.200.200:8091
 enable-degrade: false
 disable-global-transaction: false
transport:
 shutdown:
   wait: 3
 thread-factory:
   boss-thread-prefix: NettyBoss
   worker-thread-prefix: NettyServerNIOWorker
   server-executor-thread-prefix: NettyServerBizHandler
   share-boss-worker: false
   client-selector-thread-prefix: NettyClientSelector
   client-selector-thread-size: 1
   client-worker-thread-prefix: NettyClientWorkerThread
   worker-thread-size: default
   boss-thread-size: 1
 type: TCP
 server: NIO
 heartbeat: true
 serialization: seata
 compressor: none
 enable-client-batch-send-request: true
registry:
 type: nacos
 nacos:
   application: seata-server
   server-addr: 192.168.200.200:8848
   group : "SEATA_GROUP"
   namespace: "ce6c9959-8b1d-4596-b15c-22634776af3d"
   username: "nacos"
   password: "nacos"

docker run --name seata-server-n2 -p 8092:8092 -d -e SEATA_IP=192.168.200.200 -e SEATA_PORT=8092  --restart=on-failure seataio/seata-server:1.3.0

registry {
  # file ...nacos ...eureka...redis...zk...consul...etcd3...sofa
  type = "nacos"
  nacos {
    application = "seata-server"
    serverAddr = "192.168.200.200:8848"
    group = "SEATA_GROUP"
    namespace = "1ebba5f6-49da-40cc-950b-f75c8f7d07b3"
    cluster = "default"
    username = "nacos"
    password = "nacos"
  }
}

docker run --name redis6.2 --restart=on-failure -p 6379:6379 -d redis:6.2

## transaction log store, only used in seata-server
store {
  ## store mode: file...db...redis
  mode = "redis"
  ## file store property
  file {
    ## store location dir
    dir = "sessionStore"
    # branch session size , if exceeded first try compress lockkey, still exceeded throws exceptions
    maxBranchSessionSize = 16384
    # globe session size , if exceeded throws exceptions
    maxGlobalSessionSize = 512
    # file buffer size , if exceeded allocate new buffer
    fileWriteBufferCacheSize = 16384
    # when recover batch read size
    sessionReloadReadSize = 100
    # async, sync
    flushDiskMode = async
  }
  ## database store property
  db {
    ## the implement of javax.sql.DataSource, such as DruidDataSource(druid)/BasicDataSource(dbcp)/HikariDataSource(hikari) etc.
    datasource = "druid"
    ## mysql/oracle/postgresql/h2/oceanbase etc.
    dbType = "mysql"
    driverClassName = "com.mysql.jdbc.Driver"
    url = "jdbc:mysql://127.0.0.1:3306/seata"
    user = "mysql"
    password = "mysql"
    minConn = 5
    maxConn = 30
    globalTable = "global_table"
    branchTable = "branch_table"
    lockTable = "lock_table"
    queryLimit = 100
    maxWait = 5000
  }
  ## redis store property
  redis {
    host = "192.168.200.200"
    port = "6379"
    password = ""
    database = "0"
    minConn = 1
    maxConn = 10
    queryLimit = 100
  }
}