[SERVER-21979] MongoD instance came down Created: 21/Dec/15 Updated: 15/Jan/16 Resolved: 11/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James Mangold | Assignee: | Siyuan Zhou |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Repl F (01/29/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Hi. I have a 12 node sharded and replicated cluster on the GA version of 3.2. This morning a node came down and I don't know why. I am attaching the log. |
| Comments |
| Comment by James Mangold [ 14/Jan/16 ] | ||||
|
We are currently running 3.2.1. Thank you. Will you please update this when 3.2.2 is available? | ||||
| Comment by Ramon Fernandez Marina [ 13/Jan/16 ] | ||||
|
james.mangold@interactivedata.com, as Siyuan mentions above the fix for this issue will be part of the upcoming 3.2.2 release, which is scheduled for publication in about 4-6 weeks at the moment. I'd strongly encourage you to upgrade to 3.2.1, which not only contains other important fixed but should also work around the fassert() issue. Regards, | ||||
| Comment by Siyuan Zhou [ 11/Jan/16 ] | ||||
|
Resolved as dup to | ||||
| Comment by Scott Hernandez (Inactive) [ 09/Jan/16 ] | ||||
|
Yes, 3.2.1 will have the fix for this problem in | ||||
| Comment by Siyuan Zhou [ 08/Jan/16 ] | ||||
|
Talked with scotthernandez, we believe this issue is fixed by
We'll discuss the implication wrt RAFT offline. scotthernandez, do you think we can close this ticket as a dup? | ||||
| Comment by James Mangold [ 05/Jan/16 ] | ||||
|
Sorry - I meant 008... | ||||
| Comment by James Mangold [ 05/Jan/16 ] | ||||
|
004 went down in this case... | ||||
| Comment by James Mangold [ 05/Jan/16 ] | ||||
|
Hi - just getting back to this, because it happened again: I am attaching the log from the downed node and it's sync sources. Sorry - was out for xmas. | ||||
| Comment by Kelsey Schubert [ 21/Dec/15 ] | ||||
|
Hi james.mangold@interactivedata.com, To continue to investigate can you please answer the following questions:
Thank you, |