[SERVER-22115] Primary Server Crashes due to Memory Leak Created: 10/Jan/16 Updated: 11/Feb/16 Resolved: 10/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.0.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Moshe Kaplan [X] | Assignee: | Ramon Fernandez Marina |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | WTmem | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | Server details: Replica set: Primary, Secondary and Arbiter. |
| Participants: |
| Description |
|
| Comments |
| Comment by Moshe Kaplan [X] [ 11/Feb/16 ] | ||||
|
The customer is happy w/ the 3.2.1 installation and currently is not willing to put more effort into it. | ||||
| Comment by Ramon Fernandez Marina [ 10/Feb/16 ] | ||||
|
MosheKaplan, without either the ss.log file (from the 3.0 affected node) or the contents of diagnostic.data (from a 3.2 affected node) it's not possible for us to investigate further, so I'm going to close this ticket. If this is still an issue for you please provide one of the two data options requested above and we'll reopen the ticket to take a closer look. Thanks, | ||||
| Comment by Ramon Fernandez Marina [ 25/Jan/16 ] | ||||
|
MosheKaplan, if you're able to observe this behavior on a 3.2 node, can you please upload the contents of the diagnostic.data directory within your dbpath? This directory contains the same information that you collected above in the ss.log file, and should help us understand what's going on. | ||||
| Comment by Moshe Kaplan [X] [ 18/Jan/16 ] | ||||
|
Checking for that. | ||||
| Comment by Ramon Fernandez Marina [ 18/Jan/16 ] | ||||
|
Thanks for the additional information MosheKaplan; when running the script above you should have ended up with another file, ss.log, which is the one that has the key information that can help debugging this issue. Can you please upload it as well? | ||||
| Comment by Moshe Kaplan [X] [ 18/Jan/16 ] | ||||
|
Some more info: | ||||
| Comment by Moshe Kaplan [X] [ 18/Jan/16 ] | ||||
|
iostat information | ||||
| Comment by Ramon Fernandez Marina [ 11/Jan/16 ] | ||||
|
Sorry you're running into this issue MosheKaplan. In order to diagnose this problem, can you please run the following shell script while you reproduce the crash?
You can adjust the delay depending on how long this issue takes to trigger; if it's, say, 24h, the delay can be 5s to prevent the resulting files from being too large. If you could then upload the ss.log and iostat.log files along with the mongod.log for the affected server that should give us sufficient information to understand the source of the problem. Thanks, |