Fdb::fdb_exception (CommitProxy commit memory limit exceeded)

Development
1

Error code 1042 appears when I perform FDB pressure testing. At this time, the cluster is unavailable. The status json information is as follows：

sing cluster file `/etc/foundationdb/fdb.cluster'.
 
The database is unavailable; type `status' for more information.
 
Welcome to the fdbcli. For help, type `help'.
fdb> status json
 
WARNING: Long delay (Ctrl-C to interrupt)
 
{
    "client" : {
        "cluster_file" : {
            "path" : "/etc/foundationdb/fdb.cluster",
            "up_to_date" : true
        },
        "coordinators" : {
            "coordinators" : [
                {
                    "address" : "10.1.5.5:5502",
                    "protocol" : "0fdb00b071010000",
                    "reachable" : true
                },
                {
                    "address" : "10.1.5.6:5504",
                    "protocol" : "0fdb00b071010000",
                    "reachable" : true
                },
                {
                    "address" : "10.2.12.6:7501",
                    "protocol" : "0fdb00b071010000",
                    "reachable" : true
                },
                {
                    "address" : "10.3.241.5:7500",
                    "protocol" : "0fdb00b071010000",
                    "reachable" : true
                },
                {
                    "address" : "10.3.241.6:6500",
                    "protocol" : "0fdb00b071010000",
                    "reachable" : true
                }
            ],
            "quorum_reachable" : true
        },
        "database_status" : {
            "available" : false,
            "healthy" : false
        },
        "messages" : [
            {
                "description" : "Timed out fetching cluster status.",
                "name" : "status_incomplete_timeout"
            }
        ],
        "timestamp" : 1718768298
    },
    "cluster" : {
        "layers" : {
            "_valid" : false
        }
    }
}

When the pressure test is stopped, the cluster automatically returns to normal. How to avoid this situation？