[SERVER-27315] Mongo wt cache will not be reclaimed Created: 07/Dec/16 Updated: 27/Oct/23 Resolved: 13/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | liangzhang | Assignee: | Kelsey Schubert |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS release 6.6 |
||
| Attachments: |
|
| Participants: |
| Description |
|
At 18:15 this time point, wt cache continues to grow until 96%. then at 19:00, we switch primary to secondary. System environment Storage: |
| Comments |
| Comment by Kelsey Schubert [ 14/Dec/16 ] |
|
Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Kind regards, |
| Comment by liangzhang [ 14/Dec/16 ] |
|
What causes eviction to be so busy. Is a lot of update, find, findandmodify or any other reason? How can I optimize to reduce the eviction workload? |
| Comment by Kelsey Schubert [ 13/Dec/16 ] |
|
We've examined the diagnostic.data you've provided. It appears that even after the node steps down to secondary it is still under considerable load. Additionally, we see that eviction is busy working under this workload. In this case, it is expected that the secondary would continue to use cache and CPU resources. Kind regards, |
| Comment by liangzhang [ 08/Dec/16 ] |
|
Thank you for your reply, I hope you can help me solve my problems. |
| Comment by Kelsey Schubert [ 07/Dec/16 ] |
|
Would you please attach an archive of the diagnostic.data directory to this ticket so we can continue to investigate? Thank you, |