You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gsoc@community.apache.org by "Maxim Solodovnik (Jira)" <ji...@apache.org> on 2025/02/08 09:45:00 UTC
[jira] [Updated] (GSOC-274) GSoC 2025 - Apache Seata(Incubating): Extend multi-raft cluster mode
[ https://issues.apache.org/jira/browse/GSOC-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik updated GSOC-274:
----------------------------------
Labels: Seata gsoc2025 (was: gsoc2025)
> GSoC 2025 - Apache Seata(Incubating): Extend multi-raft cluster mode
> ---------------------------------------------------------------------
>
> Key: GSOC-274
> URL: https://issues.apache.org/jira/browse/GSOC-274
> Project: Comdev GSOC
> Issue Type: Wish
> Reporter: Jianbin Chen
> Priority: Major
> Labels: Seata, gsoc2025
>
> h4. Description
> *Synopsis*
> The current Apache Seata Server supports the Raft cluster mode, but the performance and throughput of the cluster are significantly limited due to the single leader in a single Raft group. Therefore, the goal is to extend Seata Server to support multi-raft capability.
>
> *Benefits to Community*
> Due to the characteristics of Raft, requests are processed on the leader node and the results are submitted to the followers through the Raft consensus protocol. As a result, a significant amount of computational load is placed on the leader node, while followers only need to receive the final computed result. This causes the CPU, memory, and other metrics of the leader to be much higher than those of the followers. Additionally, the throughput of a single leader is limited by the machine configuration of the highest-spec node in the cluster, making it difficult to balance the traffic effectively. Therefore, supporting multi-raft would make the load distribution more balanced across all nodes in the cluster, improving throughput and performance, while also reducing the waste of machine resources.
>
> *Deliverables*
> The expected delivery goal is to apply the multi-raft capability of the sofa-jraft component to Seata Server through detailed learning and practice
>
> The step expected are the following:
> * Learning and using the sofa-jraft component
> * Understanding and practicing the transaction grouping capability in Seata
> * Gaining a certain level of understanding of Seata's communication protocol
> * Gaining a certain level of understanding of Seata's storage model, especially the Raft mode
> * Ensuring compatibility between different versions
> *Useful links*
> * [seata-raft-detailed-explanation|https://seata.apache.org/blog/seata-raft-detailed-explanation]
> * [transaction-group|https://seata.apache.org/docs/next/user/txgroup/transaction-group]
> * [sofa-jraft|https://www.sofastack.tech/en/projects/sofa-jraft/overview/]
> h4. *Mentor*
> *
> ** Mentor: Jianbin Chen, Apache Seata(Incubating) PPMC Member [jianbin@apache.org|mailto:jianbin@apache.org]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: gsoc-unsubscribe@community.apache.org
For additional commands, e-mail: gsoc-help@community.apache.org