-
Type: Question
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.0.6
-
Component/s: Aggregation Framework
-
Labels:None
On a Windows machine having 64GB RAM with MongoDB 4.0 community edition, it is observed that the dirty bytes in cache reach upto .1TB and cache reaches 27GB. At this stage the C# API fetching data from MongoDB starts throwing 504 bad gateway error. As soon as the mongo service is restarted, the API starts giving results. Please help share the reason for this behavior and suggested solution for same as restarting mongo service is not an optimal solution.