In the current stats we have a scenario where cache pages selected for eviction, cache modified pages evicted, and cache pages evicted by application threads showing wiredtiger is able to select pages for eviction and have evicted them, but capacity bytes written for eviction is 0 and cache pages written requiring in-memory restoration is showing the pages are not being evicted. This is a bit confusing as the description kinda direct us to a wrong direction thinking wiredtiger is evicting pages when diagnosing help tickets.

The ticket is to investigate how these stats are calculated, and find a solution to mitigate this confusion. Possible solution may include reword the stats' description a bit, add a new stat like "pages selected for eviction unable to be evicted because of in-memory restoration" so the count of those pages evicted but are restored back to memory can be re-classified into the new stat. A STAR ticket should be created if modification on t2 is required.