raincat icon indicating copy to clipboard operation
raincat copied to clipboard

强一致分布式事务框架

Results 32 raincat issues
Sort by recently updated
recently updated
newest added

Bumps [spring-core](https://github.com/spring-projects/spring-framework) from 5.0.7.RELEASE to 5.2.22.RELEASE. Release notes Sourced from spring-core's releases. v5.2.22.RELEASE :star: New Features Refine CachedIntrospectionResults property introspection #28446 :lady_beetle: Bug Fixes Ignore invalid STOMP frame #28444 v5.2.21.RELEASE...

dependencies
java

Bumps [mysql-connector-java](https://github.com/mysql/mysql-connector-j) from 5.1.38 to 8.0.28. Changelog Sourced from mysql-connector-java's changelog. Changelog https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/ Version 8.0.29 Fix for Bug#21978230, COMMENT PARSING NOT PROPER IN PREPSTMT.EXECUTEBATCH(). Fix for Bug#81468 (23312764), MySQL server...

dependencies
java

Bumps [mysql-connector-java](https://github.com/mysql/mysql-connector-j) from 5.1.38 to 8.0.28. Changelog Sourced from mysql-connector-java's changelog. Changelog https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/ Version 8.0.29 Fix for Bug#21978230, COMMENT PARSING NOT PROPER IN PREPSTMT.EXECUTEBATCH(). Fix for Bug#81468 (23312764), MySQL server...

dependencies
java

Bumps [mysql-connector-java](https://github.com/mysql/mysql-connector-j) from 5.1.38 to 8.0.28. Changelog Sourced from mysql-connector-java's changelog. Changelog https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/ Version 8.0.29 Fix for Bug#21978230, COMMENT PARSING NOT PROPER IN PREPSTMT.EXECUTEBATCH(). Fix for Bug#81468 (23312764), MySQL server...

dependencies
java

Bumps [junit](https://github.com/junit-team/junit4) from 4.12 to 4.13.1. Release notes Sourced from junit's releases. JUnit 4.13.1 Please refer to the release notes for details. JUnit 4.13 Please refer to the release notes...

dependencies
java

在`org.dromara.raincat.core.service.impl.TxManagerLocator`中存储server列表的部分使用的是`AtomicReference`。这里的修改部分又加了锁,如果不用原子类,直接用`volatile`不可以吗。

作者你好,看了一下happylifeplat-transaction的实现,感觉你这个事务框架好像还不能算是“二阶段提交”啊。二阶段提交针对的是事务框架对资源管理器/数据库的协调过程,真正执行二阶段提交的应该还是底层的数据库。原理可以参考:[二阶段提交原理图](https://static001.infoq.cn/resource/image/76/40/76a6d8e35ec97e1723b785a13a54a940.png)。 而happylifeplat-transaction在提交事务时,采用的仍然是资源管理器的一阶段提交。只不过在发起提交之前,先判断了一下节点间网络通道的状态等信息,但这种框架自己内部的判断,应该不能算是一个提交的阶段啊。不然,二阶段提交岂不是分分钟改成三阶段提交了?二阶段、三阶段也就没啥太大差别、也不具备任何意义了。不知道我理解的对不对,求解惑~

raincat-manager起到事务协调器的作用的话 raincat-admin只是起到一个管理后台的作用吗? 为什么不把他们俩个合并成一个? 因为manager已经集成了eureka-server吗