在这个链接上有一个注意事项,allocation_size可以在512 b到128 MB之间进行调优。
我们如何修改该变量并启动具有16 4KB allocation_size的mongod进程--例如,缺省值为4KB?
这不管用
replica1:PRIMARY> db.adminCommand( { "setParameter": 1, "wiredTigerEngineRuntimeConfig": "allocation_size=64KB"}){ "ok" : 0, "errmsg" : "WiredTiger reconfiguration failed with error code (22): Invalid argument", "code" : 2, "codeName" : "BadValue"}
replica1:PRIMARY> db.createCollection( "users", { storageEngine: { wiredTiger: { configString: "allocation_size=64KB" } } } ){ "ok" : 0, "errmsg" : "22: Invalid argument", "code" : 2, "codeName" : "BadValue"}发布于 2022-05-15 21:55:48
修改参数的方式是正确的。错误消息是关于另一个问题的。默认值分别为4KB和32 4KB的参数internal_page_max和leaf_page_max必须是allocation_size的倍数。在设置allocation_size时必须确保这一点。因此,在您的示例中,如果要将allocation_size设置为64 as,则必须将其他两个设置为至少64 as,如下所示:
rs0:PRIMARY> db.createCollection( "users", { storageEngine: { wiredTiger: { configString: "allocation_size=64KB,internal_page_max=64KB,leaf_page_max=64KB" } } } ) {
"ok" : 1,
"$clusterTime" : {
"clusterTime" : Timestamp(1595909936, 1),
"signature" : {
"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
"keyId" : NumberLong(0)
}
},
"operationTime" : Timestamp(1595909936, 1) }来源和示例:WT-6510
https://stackoverflow.com/questions/62975989
复制相似问题