MongoDB Jira系列-3.0.6修复的那些事儿

大家好，我是E叔。

经常有朋友向我咨询版本选型的问题。

受到老毕同学的启发，E叔决定为大家搬运+翻译+简单解释 MongoDB3.0.4+以后各个版本fixed的比较重要的jira issues。大家可以根据需求来决定版本选型。

今天是3.0.6篇。

Issues fixed in 3.0.6

以下均是3.0.6中修复了的jira issues。（比较重要的issues）

由于人肉整理，难免有遗漏，欢迎补充。

SERVER-20248

与连接数&session有关的内存泄露一则

SERVER-19987

每个mongo与wt的session都做了cursor cache（此前没有，易造成内存泄露）

SERVER-19751

WT panic halt

SERVER-19673，WT-2007

Wt log cache内存泄露。

db.serverStatus().wiredTiger.log[‘total log buffer size’]的返回是WT journal使用的内存，但是不受WT cache 设置的限制，如果特别大了，可能会造成OOM，修复后将限制其大小

Each log slot has a buffer associated with it. That buffer is grown dynamically until it is large enough to hold the consolidated records.

We recently bumped the number of slots, which may alter how much memory log buffers consume.

We should consider limiting how much memory the log system can use (maybe a log cache size?). Or alternatively limiting the size log buffers can grow to – there is almost certainly a limit to how much memory it makes sense to copy and consolidate into a buffer rather than just writing it directly.

SERVER-19573

WT crash一则

SERVER-19538

SSL 与 Auditing 的issue 一则

SERVER-19522

Capped collection 插入效率的fix

SERVER-19464

aggregate的$sort将不会关闭connection

The sort stage doesn’t properly close the connection. This causes it to be marked as bad and not returned to the pool which leads to many log lines and connection churn. Potentially gigs per hour of log lines on a small cluster.