Pengfan Lu

@acelyc111 Thanks, I will take your advice and get it done as soon as possible.

This is the app creation process, I show the app envs passing through the num_levels option. 

 This is the specific creation process of replica, including my two modifications. Respectively deal with creating a new rocksdb and restarting rocksdb. ### Create a replica key process：...

I show the set_app_envs procedure using the write_buffer_size option. My third modification solves the online modification of dynamic rocksdb options. 

You can follow dockerfile to build. https://github.com/apache/incubator-pegasus/blob/master/docker/pegasus-build-env/ubuntu2004/Dockerfile Try update maven settings to build. ```shell sudo cp /usr/share/maven/conf/settings.xml /usr/share/maven/conf/settings.xmlold sudo vim /usr/share/maven/conf/settings.xml ``` ```c++ nexus-tencentyun * Nexus tencent下·yun http://mirrors.cloud.tencent.com/nexus/repository/maven-public/ ```

First, follow this [link](https://github.com/apache/incubator-pegasus/blob/master/docker/pegasus-build-env/ubuntu2004/Dockerfile) to build the environment. If the build is successful, proceed to build incubator-pegasus-2.5 using CentOS 7.

@acelyc111 “Feel free to translate this site at first.” is mean translate to Chinese？

I found that `max_copy_rate_megabytes_per_disk` causes group check timeouts, leading to primary replica shard ballot growth. Some nodes are generating core dumps, and in severe cases, unalive nodes will appear. This...

`max_copy_rate_megabytes_per_disk` causes a large number of threads in the `replica.default` thread pool to sleep. The `nfs_service_impl::on_copy` working on `replica.default` can also cause this issue. In this thread pool: 1. affecting...

The aforementioned phenomenon is one of issues triggered by bulkload download. # Phenomenon 1. Doing bulkload (download sst file stage) with any action which need to **restart ONE node**,may cause...