-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.16
-
Component/s: Performance, Stability, WiredTiger
-
None
-
ALL
Yesterday, we had multiple slowdown on our primary server:
From our metrics, we can see that the cache evictions threads were not able to evict cache fast enough until the cache used reached 95% and that applications threads started to help the dedicated threads (source: http://source.wiredtiger.com/mongodb-3.4/tune_cache.html):
We already encountered this issue with mongo 3.2 two years ago (on the secondary server though) and the only thing that fixed the issue was to upgrade to mongo 3.4: https://jira.mongodb.org/browse/SERVER-27700
We plan to upgrade to mongo 3.6 in the following months but can you check that a regression has not be introduced in our current mongo version ?
Another related ticket: https://jira.mongodb.org/browse/SERVER-27753
I can provide you diagnostic.data and slow log files. Thx for you help.
- is related to
-
SERVER-42698 WT Cache eviction server performance regression in 3.6.13 (compared to 3.4.16)
- Closed