0


SpringCloud整合Seata1.6.1部署与使用Nacos方式

SpringCloud整合Seata1.6.1部署与使用Nacos方式

seata官网:http://seata.io/zh-cn/index.html
seata-server: https://github.com/seata/seata/releases
SpringCloud整合Seata出现异常数据未回滚的解决方案

二. seata-server配置

1.1 下载seater-server

下载指定版本seata-server,本案例使用

  1. v1.6.1

版本。

1.2 修改seata/conf/application.yml配置文件(已删除无用配置)

  1. server:port:7091spring:application:name: seata-server # seata-server服务名logging:config: classpath:logback-spring.xml
  2. file:path: ${user.home}/seata/runlogs # 指定日志路径extend:logstash-appender:destination: 127.0.0.1:4560kafka-appender:bootstrap-servers: 127.0.0.1:9092topic: logback_to_logstash
  3. # seata可视化web界面账号密码console:user:username: seata
  4. password: seata
  5. seata:# 配置中心config:# support: nacos, consul, apollo, zk, etcd3type: nacos # 指定配置中心为nacosnacos:server-addr: 127.0.0.1:8848# nacos的ip端口group: DEFAULT_GROUP # 对应的组,默认为DEFAULT_GROUPnamespace: a090b021-160c-42fb-98de-b1f9a5619d97 # 对应的命名空间,在nacos中配置username: nacos
  6. password: nacos
  7. data-id: seataServer.properties # nacos中存放seata的配置文件,后面会提该文件的使用方式,相当于seata服务启动的时候需要注册到nacos,并使用nacos中的配置文件# 注册中心与上述config同理registry:# support: nacos, eureka, redis, zk, consul, etcd3, sofatype: nacos
  8. nacos:application: seata-server
  9. server-addr: 127.0.0.1:8848namespace: a090b021-160c-42fb-98de-b1f9a5619d97
  10. group: DEFAULT_GROUP
  11. cluster: default
  12. username: nacos
  13. password: nacos
  14. security:secretKey: SeataSecretKey0c382ef121d778043159209298fd40bf3850a017
  15. tokenValidityInMilliseconds:1800000ignore:urls: /,/**/*.css,/**/*.js,/**/*.html,/**/*.map,/**/*.svg,/**/*.png,/**/*.ico,/console-fe/public/**,/api/v1/auth/login

【注意】

  • seata.config.typeseata.registry.type 都要修改为nacos
  • 修改configregistry中nacos的配置,其中namespacegroup须提前在nacos中进行配置

二. nacos配置

2.1 新建namespace

新建

  1. namespace

命名空间,需与上述

  1. seata-server

  1. application.yml

中配置一致

2.2 新建seata的seataServer.properties配置文件

在上述

  1. namespace

下新建

  1. application.yml

  1. seata.config.nacos.data-id

提到的配置文件:

  1. seataServer.properties

seataServer.properties 已删除无用配置

  1. #For details about configuration items, see https://seata.io/zh-cn/docs/user/configurations.html
  2. #Transport configuration, for client and server
  3. transport.type=TCP
  4. transport.server=NIO
  5. transport.heartbeat=true
  6. transport.enableTmClientBatchSendRequest=false
  7. transport.enableRmClientBatchSendRequest=true
  8. transport.enableTcServerBatchSendResponse=false
  9. transport.rpcRmRequestTimeout=30000
  10. transport.rpcTmRequestTimeout=30000
  11. transport.rpcTcRequestTimeout=30000
  12. transport.threadFactory.bossThreadPrefix=NettyBoss
  13. transport.threadFactory.workerThreadPrefix=NettyServerNIOWorker
  14. transport.threadFactory.serverExecutorThreadPrefix=NettyServerBizHandler
  15. transport.threadFactory.shareBossWorker=false
  16. transport.threadFactory.clientSelectorThreadPrefix=NettyClientSelector
  17. transport.threadFactory.clientSelectorThreadSize=1
  18. transport.threadFactory.clientWorkerThreadPrefix=NettyClientWorkerThread
  19. transport.threadFactory.bossThreadSize=1
  20. transport.threadFactory.workerThreadSize=default
  21. transport.shutdown.wait=3
  22. transport.serialization=seata
  23. transport.compressor=none
  24. #Transaction routing rules configuration, only for the client
  25. # 此处的mygroup名字可以自定义,只修改这个值即可
  26. service.vgroupMapping.mygroup=default
  27. #If you use a registry, you can ignore it
  28. service.default.grouplist=127.0.0.1:8091
  29. service.enableDegrade=false
  30. service.disableGlobalTransaction=false
  31. #Transaction rule configuration, only for the client
  32. client.rm.asyncCommitBufferLimit=10000
  33. client.rm.lock.retryInterval=10
  34. client.rm.lock.retryTimes=30
  35. client.rm.lock.retryPolicyBranchRollbackOnConflict=true
  36. client.rm.reportRetryCount=5
  37. client.rm.tableMetaCheckEnable=true
  38. client.rm.tableMetaCheckerInterval=60000
  39. client.rm.sqlParserType=druid
  40. client.rm.reportSuccessEnable=false
  41. client.rm.sagaBranchRegisterEnable=false
  42. client.rm.sagaJsonParser=fastjson
  43. client.rm.tccActionInterceptorOrder=-2147482648
  44. client.tm.commitRetryCount=5
  45. client.tm.rollbackRetryCount=5
  46. client.tm.defaultGlobalTransactionTimeout=60000
  47. client.tm.degradeCheck=false
  48. client.tm.degradeCheckAllowTimes=10
  49. client.tm.degradeCheckPeriod=2000
  50. client.tm.interceptorOrder=-2147482648
  51. client.undo.dataValidation=true
  52. client.undo.logSerialization=jackson
  53. client.undo.onlyCareUpdateColumns=true
  54. server.undo.logSaveDays=7
  55. server.undo.logDeletePeriod=86400000
  56. client.undo.logTable=undo_log
  57. client.undo.compress.enable=true
  58. client.undo.compress.type=zip
  59. client.undo.compress.threshold=64k
  60. #For TCC transaction mode
  61. tcc.fence.logTableName=tcc_fence_log
  62. tcc.fence.cleanPeriod=1h
  63. #Log rule configuration, for client and server
  64. log.exceptionRate=100
  65. #Transaction storage configuration, only for the server. The file, db, and redis configuration values are optional.
  66. # 默认为file,一定要改为db,我们自己的服务启动会连接不到seata
  67. store.mode=db
  68. store.lock.mode=db
  69. store.session.mode=db
  70. #Used for password encryption
  71. #These configurations are required if the `store mode` is `db`. If `store.mode,store.lock.mode,store.session.mode` are not equal to `db`, you can remove the configuration block.
  72. # 修改mysql的配置
  73. store.db.datasource=druid
  74. store.db.dbType=mysql
  75. store.db.driverClassName=com.mysql.cj.jdbc.Driver
  76. # 指定seata的数据库,下面会提
  77. store.db.url=jdbc:mysql://127.0.0.1:3306/seata?useUnicode=true&rewriteBatchedStatements=true
  78. store.db.user=root
  79. store.db.password=banmajio
  80. store.db.minConn=5
  81. store.db.maxConn=30
  82. store.db.globalTable=global_table
  83. store.db.branchTable=branch_table
  84. store.db.distributedLockTable=distributed_lock
  85. store.db.queryLimit=100
  86. store.db.lockTable=lock_table
  87. store.db.maxWait=5000
  88. #Transaction rule configuration, only for the server
  89. server.recovery.committingRetryPeriod=1000
  90. server.recovery.asynCommittingRetryPeriod=1000
  91. server.recovery.rollbackingRetryPeriod=1000
  92. server.recovery.timeoutRetryPeriod=1000
  93. server.maxCommitRetryTimeout=-1
  94. server.maxRollbackRetryTimeout=-1
  95. server.rollbackRetryTimeoutUnlockEnable=false
  96. server.distributedLockExpireTime=10000
  97. server.xaerNotaRetryTimeout=60000
  98. server.session.branchAsyncQueueSize=5000
  99. server.session.enableBranchAsyncRemove=false
  100. server.enableParallelRequestHandle=false
  101. #Metrics configuration, only for the server
  102. metrics.enabled=false
  103. metrics.registryType=compact
  104. metrics.exporterList=prometheus
  105. metrics.exporterPrometheusPort=9898

【注意】

  1. 修改service.vgroupMapping.mygroup=default该值,其中mygroup可以自定义,后面我们自己的服务启动时,配置文件中需要指定该group。
  2. 修改store.mode``````store.lock.mode``````store.session.mode这三个值为db,才能让seata连接到下面的数据库中。
  3. 修改store.db配置项下的配置,连接到自己的数据库。
  4. 该文件参数的具体作用参考官网:seata配置文件详解(官网)
  5. 该配置源文件存放在seata目录下:seata/script/config-center/config.txt

三. MySQL配置

3.1 新建seata数据库

  1. 数据库的名称

与上述

  1. 3.2

seata配置文件中的

  1. store.db.url

保持一致。

3.2 新建seata配置表

在上述库中添加seata的配置表,sql文件存放在:

  1. seata/script/server/db/mysql.sql

  1. -- -------------------------------- The script used when storeMode is 'db' ---------------------------------- the table to store GlobalSession dataCREATETABLEIFNOTEXISTS`global_table`(`xid`VARCHAR(128)NOTNULL,`transaction_id`BIGINT,`status`TINYINTNOTNULL,`application_id`VARCHAR(32),`transaction_service_group`VARCHAR(32),`transaction_name`VARCHAR(128),`timeout`INT,`begin_time`BIGINT,`application_data`VARCHAR(2000),`gmt_create`DATETIME,`gmt_modified`DATETIME,PRIMARYKEY(`xid`),KEY`idx_status_gmt_modified`(`status`,`gmt_modified`),KEY`idx_transaction_id`(`transaction_id`))ENGINE=InnoDBDEFAULTCHARSET= utf8mb4;-- the table to store BranchSession dataCREATETABLEIFNOTEXISTS`branch_table`(`branch_id`BIGINTNOTNULL,`xid`VARCHAR(128)NOTNULL,`transaction_id`BIGINT,`resource_group_id`VARCHAR(32),`resource_id`VARCHAR(256),`branch_type`VARCHAR(8),`status`TINYINT,`client_id`VARCHAR(64),`application_data`VARCHAR(2000),`gmt_create`DATETIME(6),`gmt_modified`DATETIME(6),PRIMARYKEY(`branch_id`),KEY`idx_xid`(`xid`))ENGINE=InnoDBDEFAULTCHARSET= utf8mb4;-- the table to store lock dataCREATETABLEIFNOTEXISTS`lock_table`(`row_key`VARCHAR(128)NOTNULL,`xid`VARCHAR(128),`transaction_id`BIGINT,`branch_id`BIGINTNOTNULL,`resource_id`VARCHAR(256),`table_name`VARCHAR(32),`pk`VARCHAR(36),`status`TINYINTNOTNULLDEFAULT'0'COMMENT'0:locked ,1:rollbacking',`gmt_create`DATETIME,`gmt_modified`DATETIME,PRIMARYKEY(`row_key`),KEY`idx_status`(`status`),KEY`idx_branch_id`(`branch_id`),KEY`idx_xid`(`xid`))ENGINE=InnoDBDEFAULTCHARSET= utf8mb4;CREATETABLEIFNOTEXISTS`distributed_lock`(`lock_key`CHAR(20)NOTNULL,`lock_value`VARCHAR(20)NOTNULL,`expire`BIGINT,primarykey(`lock_key`))ENGINE=InnoDBDEFAULTCHARSET= utf8mb4;INSERTINTO`distributed_lock`(lock_key, lock_value, expire)VALUES('AsyncCommitting',' ',0);INSERTINTO`distributed_lock`(lock_key, lock_value, expire)VALUES('RetryCommitting',' ',0);INSERTINTO`distributed_lock`(lock_key, lock_value, expire)VALUES('RetryRollbacking',' ',0);INSERTINTO`distributed_lock`(lock_key, lock_value, expire)VALUES('TxTimeoutCheck',' ',0);

3.3 业务数据库添加undo_log表

  1. -- 注意此处0.3.0+ 增加唯一索引 ux_undo_logCREATETABLE`undo_log`(`id`bigint(20)NOTNULLAUTO_INCREMENT,`branch_id`bigint(20)NOTNULL,`xid`varchar(100)NOTNULL,`context`varchar(128)NOTNULL,`rollback_info`longblobNOTNULL,`log_status`int(11)NOTNULL,`log_created`datetimeNOTNULL,`log_modified`datetimeNOTNULL,`ext`varchar(100)DEFAULTNULL,PRIMARYKEY(`id`),UNIQUEKEY`ux_undo_log`(`xid`,`branch_id`))ENGINE=InnoDBAUTO_INCREMENT=1DEFAULTCHARSET=utf8;

4. seata-server启动

seata 的 /bin 目录下 :/seata/bin 执行下面的脚本

  1. sh seata-server.sh -p 8091 -h 127.0.0.1

参数解释:
-h: 将地址暴露给注册中心,其他服务可以访问seata服务器
-p:要侦听的端口

并且查看

  1. nacos

中的服务注册中心是否可以看到

  1. seata-server

在这里插入图片描述

至此,seater-server的配置与部署完成

五. SpringCloud整合Seata

5.1 pom.xml依赖引入

  1. <!-- 注意一定要引入对版本,要引入spring-cloud版本seata,而不是springboot版本的seata--><dependency><groupId>com.alibaba.cloud</groupId><artifactId>spring-cloud-starter-alibaba-seata</artifactId><!-- 排除掉springcloud默认的seata版本,以免版本不一致出现问题--><exclusions><exclusion><groupId>io.seata</groupId><artifactId>seata-spring-boot-starter</artifactId></exclusion><exclusion><groupId>io.seata</groupId><artifactId>seata-all</artifactId></exclusion></exclusions></dependency><!-- 上面排除掉了springcloud默认色seata版本,此处引入和seata-server版本对应的seata包--><dependency><groupId>io.seata</groupId><artifactId>seata-spring-boot-starter</artifactId><version>1.6.1</version></dependency>

5.2 bootstrap.yml

配置文件中加入以下配置

  1. seata:tx-service-group: mygroup # 事务分组名称,要和服务端对应service:vgroup-mapping:mygroup: default # key是事务分组名称 value要和服务端的机房名称保持一致

5.3 启动服务

我们自己的服务要与

  1. seata-server

服务在同一个

  1. namespace


查看服务是否启动成功
查看nacos的对应的namespace中服务是否注册成功

5.4 使用

在外层接口上增加

  1. @GlobalTransactional

注解

  1. @GetMapping("/remoteTest")@GlobalTransactionalpublicStringremoteTest(){
  2. orderService.remoteTest();return"order success";}

只需要在最外层方法上添加注解即可,子事务方法上不需要添加

  1. @GlobalTransactional

  1. @Transactional

注解。


本文转载自: https://blog.csdn.net/weixin_40777510/article/details/129685726
版权归原作者 banmajio 所有, 如有侵权,请联系我们删除。

“SpringCloud整合Seata1.6.1部署与使用Nacos方式”的评论:

还没有评论