seata快速開始

seata版本為1.5.2,要關(guān)注版本,因為版本之間的差距很大.
官網(wǎng)地址:http://seata.io/zh-cn/
server源碼:https://github.com/seata/seata
seata-server下載:
百度下載
鏈接：https://pan.baidu.com/s/1eilbSI0YdmupHYI7FroTsw
提取碼：biam
github下載:
https://github.com/seata/seata/releases
nacos下載地址：https://github.com/alibaba/nacos/releases
百度網(wǎng)盤下載地址
鏈接：https://pan.baidu.com/s/1I4Z-vVrTTch6p4Z1FhIkOQ
提取碼：g7hg
實例代碼:
https://gitee.com/zhangjijige/springcloudalibaba.git
代碼是借鑒來的,稍微改了一下
本文使用的AT的方式實現(xiàn)分布式事務(wù),也是最經(jīng)常使用一種模式,至于其余的模式這里就不闡述了,配置中心使用nacos,seata-server(事務(wù)協(xié)調(diào)者)使用mysql的方式存儲,性能會有寫損失,但是穩(wěn)定性好一些,也是比較常用的方式,什么是seata都可以取官網(wǎng)了解一下.
1.創(chuàng)建數(shù)據(jù)庫

image.png

sql語句在項目中
2.創(chuàng)建seata-server(事務(wù)協(xié)調(diào)者)
配置文件

server:
  port: 7091

spring:
  application:
    name: seata-server

logging:
  config: classpath:logback-spring.xml
  file:
    path: ${user.home}/logs/seata
  extend:
    logstash-appender:
      destination: 127.0.0.1:4560
    kafka-appender:
      bootstrap-servers: 127.0.0.1:9092
      topic: logback_to_logstash
#1.5提供了可視化界面,用戶名和密碼
console:
  user:
    username: seata
    password: seata

seata:
  config:
    # support: nacos, consul, apollo, zk, etcd3
    type: nacos
    nacos:
      server-addr: 127.0.0.1:8848
      namespace:
      group: SEATA_GROUP
      username:
      password:
      ##if use MSE Nacos with auth, mutex with username/password attribute
      #access-key: ""
      #secret-key: ""
      data-id: seataServer.properties
  registry:
    # support: nacos, eureka, redis, zk, consul, etcd3, sofa
    type: nacos
    nacos:
      application: seata-server
      server-addr: 127.0.0.1:8848
      group: SEATA_GROUP
      namespace:
      cluster: default(這里后續(xù)提到很重要的配置)
      username:
      password:
      ##if use MSE Nacos with auth, mutex with username/password attribute
      #access-key: ""
      #secret-key: ""
  security:
    secretKey: SeataSecretKey0c382ef121d778043159209298fd40bf3850a017
    tokenValidityInMilliseconds: 1800000
    ignore:
      urls: /,/**/*.css,/**/*.js,/**/*.html,/**/*.map,/**/*.svg,/**/*.png,/**/*.ico,/console-fe/public/**,/api/v1/auth/login

啟動seata-server
seata-server.bat
3.啟動nacos
注意在seata-server的配置文件中,data-id: seataServer.properties配置
nacos的啟動本文就是使用單機啟動
startup.cmd -m standalone
nacos的命名空間就使用默認(rèn)的public,在配置的namespace為空就可以了
創(chuàng)建配置


image.png

service.vgroupMapping.default_tx_group=default這個配置很重要

#這個很重要,要不然事務(wù)不起作用
#default_tx_group和default,defaule是seata-server中  registry:中cluster的數(shù)值
#default_tx_group是資源服務(wù),就是寫業(yè)務(wù)的服務(wù)的配置  tx-service-group: default_tx_group
service.vgroupMapping.default_tx_group=default
service.enableDegrade=false
service.disableGlobalTransaction=false
#Transaction storage configuration, only for the server. The file, DB, and redis configuration values are optional.
store.mode=db
store.lock.mode=db
store.session.mode=db
#Used for password encryption
#store.publicKey=
#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.
store.db.datasource=druid
store.db.dbType=mysql
store.db.driverClassName=com.mysql.cj.jdbc.Driver
store.db.url=jdbc:mysql://127.0.0.1:3306/seata?useUnicode=true&rewriteBatchedStatements=true
store.db.user=root
store.db.password=root
store.db.minConn=5
store.db.maxConn=30
store.db.globalTable=global_table
store.db.branchTable=branch_table
store.db.distributedLockTable=distributed_lock
store.db.queryLimit=100
store.db.lockTable=lock_table
store.db.maxWait=5000
#Transaction rule configuration, only for the server
server.recovery.committingRetryPeriod=1000
server.recovery.asynCommittingRetryPeriod=1000
server.recovery.rollbackingRetryPeriod=1000
server.recovery.timeoutRetryPeriod=1000
server.maxCommitRetryTimeout=-1
server.maxRollbackRetryTimeout=-1
server.rollbackRetryTimeoutUnlockEnable=false
server.distributedLockExpireTime=10000
server.xaerNotaRetryTimeout=60000
server.session.branchAsyncQueueSize=5000
server.session.enableBranchAsyncRemove=false
#Transaction rule configuration, only for the client
client.rm.asyncCommitBufferLimit=10000
client.rm.lock.retryInterval=10
client.rm.lock.retryTimes=30
client.rm.lock.retryPolicyBranchRollbackOnConflict=true
client.rm.reportRetryCount=5
client.rm.tableMetaCheckEnable=true
client.rm.tableMetaCheckerInterval=60000
client.rm.sqlParserType=druid
client.rm.reportSuccessEnable=false
client.rm.sagaBranchRegisterEnable=false
client.rm.sagaJsonParser=fastjson
client.rm.tccActionInterceptorOrder=-2147482648
client.tm.commitRetryCount=5
client.tm.rollbackRetryCount=5
client.tm.defaultGlobalTransactionTimeout=60000
client.tm.degradeCheck=false
client.tm.degradeCheckAllowTimes=10
client.tm.degradeCheckPeriod=2000
client.tm.interceptorOrder=-2147482648
client.undo.dataValidation=true
client.undo.logSerialization=jackson
client.undo.onlyCareUpdateColumns=true
server.undo.logSaveDays=7
server.undo.logDeletePeriod=86400000
client.undo.logTable=undo_log
client.undo.compress.enable=true
client.undo.compress.type=zip
client.undo.compress.threshold=64k
#For TCC transaction mode
tcc.fence.logTableName=tcc_fence_log
tcc.fence.cleanPeriod=1h
#Log rule configuration, for client and server
log.exceptionRate=100
#Metrics configuration, only for the server
metrics.enabled=false
metrics.registryType=compact
metrics.exporterList=prometheus
metrics.exporterPrometheusPort=9898
#For details about configuration items, see https://seata.io/zh-cn/docs/user/configurations.html
#Transport configuration, for client and server
transport.type=TCP
transport.server=NIO
transport.heartbeat=true
transport.enableTmClientBatchSendRequest=false
transport.enableRmClientBatchSendRequest=true
transport.enableTcServerBatchSendResponse=false
transport.rpcRmRequestTimeout=30000
transport.rpcTmRequestTimeout=30000
transport.rpcTcRequestTimeout=30000
transport.threadFactory.bossThreadPrefix=NettyBoss
transport.threadFactory.workerThreadPrefix=NettyServerNIOWorker
transport.threadFactory.serverExecutorThreadPrefix=NettyServerBizHandler
transport.threadFactory.shareBossWorker=false
transport.threadFactory.clientSelectorThreadPrefix=NettyClientSelector
transport.threadFactory.clientSelectorThreadSize=1
transport.threadFactory.clientWorkerThreadPrefix=NettyClientWorkerThread
transport.threadFactory.bossThreadSize=1
transport.threadFactory.workerThreadSize=default
transport.shutdown.wait=3
transport.serialization=seata
transport.compressor=none

3.資源服務(wù)(業(yè)務(wù)服務(wù))
這里要說明的是seata的配置了 nacos,項目本身也配置了nacos,兩個配置都是需要的,
注意seata-server的nacos的group和資源服務(wù)的group要保持一致,具體看git上的項目的配置,沒有需要特殊說明的.
4.使用
AT模式的使用,還是比較簡單的,只需要在服務(wù)調(diào)用的發(fā)起方標(biāo)注
@GlobalTransactional注解即可
這里舉例要回滾的
seata.controller.TestController#testCommit方法被@GlobalTransactional標(biāo)注
更新stock表
productService.reduceStock(id, totalAmount);
新增訂單
orderService.save(orders);
新增訂單的方法寫了一個 10/0的代碼,報錯誤
方法調(diào)用前


image.png

debug到orderService.save(orders);


image.png

此時stock表發(fā)生變化
image.png

由86變成84
看一下undolog表的rollback_info字段數(shù)據(jù),存儲了原數(shù)據(jù)和修改后的數(shù)據(jù) 
{"@class":"io.seata.rm.datasource.undo.BranchUndoLog","xid":"172.17.171.135:8091:4602985123575644297","branchId":4602985123575644299,"sqlUndoLogs":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.undo.SQLUndoLog","sqlType":"UPDATE","tableName":"stock","beforeImage":{"@class":"io.seata.rm.datasource.sql.struct.TableRecords","tableName":"stock","rows":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.sql.struct.Row","fields":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"id","keyType":"PRIMARY_KEY","type":4,"value":1},{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"count","keyType":"NULL","type":4,"value":86}]]}]]},"afterImage":{"@class":"io.seata.rm.datasource.sql.struct.TableRecords","tableName":"stock","rows":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.sql.struct.Row","fields":["java.util.ArrayList",[{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"id","keyType":"PRIMARY_KEY","type":4,"value":1},{"@class":"io.seata.rm.datasource.sql.struct.Field","name":"count","keyType":"NULL","type":4,"value":84}]]}]]}}]]}

繼續(xù)調(diào)用orderService.save(orders);方法會報錯誤,整個事務(wù)回滾,stock表就會歸滾到86
這樣分布式事務(wù)結(jié)束.
還有很多的情況,比如人為的把stoke的數(shù)據(jù)改一下, 86 全局事務(wù)改為84,人為改為80,當(dāng)事務(wù)回滾的時候,數(shù)據(jù)怎么恢復(fù),還有全局事務(wù)沒有提交的情況下,其實數(shù)據(jù)是已經(jīng)發(fā)生了變化,那這個時候,另一個事務(wù)讀取數(shù)據(jù)是多少后續(xù)的文章會分析.

?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
【社區(qū)內(nèi)容提示】社區(qū)部分內(nèi)容疑似由AI輔助生成，瀏覽時請結(jié)合常識與多方信息審慎甄別。
平臺聲明：文章內(nèi)容（如有圖片或視頻亦包括在內(nèi)）由作者上傳并發(fā)布，文章內(nèi)容僅代表作者本人觀點，簡書系信息發(fā)布平臺，僅提供信息存儲服務(wù)。

相關(guān)閱讀更多精彩內(nèi)容

友情鏈接更多精彩內(nèi)容