Hi Pengfan and Devs, Thank you very much, Pengfan, for the suggestion and for putting together the feature and bugfix list!
I agree that having a new release is necessary, and preparing a maintenance release on the 2.5 branch appears to be the most practical and reasonable option at this stage. It is also important for us to keep the 2.5 branch in a well-maintained state. >From the items listed so far, most of the changes are related to duplication and bulk load, which are both important features. Since the 2.5.0 release, quite a few duplication-related bug fixes have already been merged, and including them in a maintenance release would be valuable for users. I think moving forward in this direction makes sense. Meanwhile, I will also review recent changes to see whether there are other important fixes that should be considered for inclusion. In general, for a maintenance release, we should focus on important bug fixes and possibly small, safe improvements, while avoiding behavioral changes on the 2.5 branch. Please feel free to share any additional suggestions or missing items that should be considered for this release. Thanks again for initiating this discussion! Best regards, Dan On Thu, Feb 12, 2026 at 4:23 PM lu_peng_fan <[email protected]> wrote: > Hi Devs, > > It has been quite some time since the last 2.5.0 release. The master > branch currently has several major features in progress, including FQDN > support and the new metrics framework. They are not yet complete. > Therefore, we are considering a maintenance release 2.5.1 based on the 2.5 > branch. This will deliver important improvements and fixes to users. > > Proposed Features and Improvements for 2.5.1: > > Features > > Support JuiceFS as a Block Service > Pegasus now supports JuiceFS as a block service backend. JuiceFS can store > data on public cloud object storage. It offers a more cost-effective > alternative to HDFS. > > Bug Fixes (Critical) > > > Duplication Stability Improvements > We have fixed a series of duplication bugs: > > These fixes significantly improve the robustness of duplication under > failure, rebalance, and restart scenarios. > > > Duplication conflicts during cluster rebalancing > > Missing or inconsistent duplication status persistence > > Crashes caused by duplication manager lifecycle issues > > Duplication getting stuck in certain states after errors > > Conflicts between duplication and bulkload operations > > > Bulkload Reliability Fixes > > > Fixed an issue where ingest could hang when encountering write throttling > > Fixed loss of ingest_behind arguments during load balance > > Reduced partition ingest time to improve bulkload performance > > > Replica Startup & Configuration Fixes > > > Fixed incorrect database existence checks when starting replicas > > Fixed issues where string-type gflags could not be updated correctly > > Fixed command availability issues (for example, app_stat) > > Improvements & Refactors > > Duplication Codebase Improvements > > Reduced latency before the last mutation is duplicated to remote clusters > > > > > Some of them have not yet been merged into the master branch. Examples > include duplication-related fixes. We believe they are important. We will > merge them into the master branch first. Then we will cherry-pick them into > this release branch. We would like to hear the community's opinion on > whether to include them. > > We welcome your feedback on this proposed feature list. Please feel free > to suggest any additions or modifications. > > Thank you for your support! > Best regards
