MongoDB version: 4.2, replica set
Problem: primary node cache evict not work.

The user's write operations were blocked because of the wiredTiger write ticket runs out. At 2020-10-07 01:24, the user inserts traffic increase so the CPU usage, dirty cache, and some metrics increase(the dirty cache percentage > 20%). And some slow log generated. However, after 01:27, there is almost no traffic, but the write ticket, CPU, dirty cache, WiredTiger hazard point check entry walked are still abnormal. It looks like the cache evict is not work, but as we look at the CPU profiling, the evict threads were still running.

This situation was resolved at about 10-07 18:00 when the replica set restarted.

We also attach the log which is not the raw log but collected by our log gathering platform because the raw log is rotated.

Please let me known if you guys want more information.