[SERVER-30089] Arbiter crash with invariant failure i < _members.size() Created: 11/Jul/17 Updated: 21/Mar/18 Resolved: 18/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.4.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andreas Kohn | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
I just noticed this in my log files of an arbiter in a replica set with 2 other nodes. I'm not exactly sure which action caused this, at the time of it occuring I was doing tests that involved stopping/starting the VM that run MongoDB. The stack trace looks similar but not identical to The arbiter (and all other members) got restarted automatically, and seemingly the setup "recovered" without additional user interaction. Set up: I'm reporting this mainly to provide a data point, given that this is a test setup it is hard to reproduce the issue in any meaningful way. |
| Comments |
| Comment by Kelsey Schubert [ 20/Mar/18 ] | |||||||||||||||||||||||||||||||||||||
|
Hi agamdua, Thanks for the report and stacktrace. This issue appears to be duplicate of the very closely related ticket, Kind regards, | |||||||||||||||||||||||||||||||||||||
| Comment by Agam Dua [ 19/Mar/18 ] | |||||||||||||||||||||||||||||||||||||
|
I had what looks to be the same issue:
This happened when I did an `rs.remove()` action for this node. Our data dog graphs show a memory spike and then it recovered, mostly because the process got killed. Let me know if you need more information than this. | |||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 18/Aug/17 ] | |||||||||||||||||||||||||||||||||||||
|
Hi ankon, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, | |||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 21/Jul/17 ] | |||||||||||||||||||||||||||||||||||||
|
Hi ankon, We still need additional information to diagnose the problem. If this is still an issue for you, would you please provide the information I requested in the previous comment? Thank you, | |||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 11/Jul/17 ] | |||||||||||||||||||||||||||||||||||||
|
Hi ankon, Thank for reporting this issue; we're looking into it. To help us investigate this issue, would you please provide the following information?
I've created a secure upload portal where you can upload these files. Files uploaded to this portal are only visible to MongoDB employees investigating this issue and are routinely deleted. Thanks again for your help, | |||||||||||||||||||||||||||||||||||||
| Comment by Andreas Kohn [ 11/Jul/17 ] | |||||||||||||||||||||||||||||||||||||
|