[SERVER-17689] Fatal assertion during replication, and/or initial sync Created: 23/Mar/15 Updated: 19/Sep/15 Resolved: 23/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, WiredTiger |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 3.0.5, 3.1.2 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Sjoerd Mulder | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Completed: | |||||||||||||||||||||
| Steps To Reproduce: | 1. Use the rolling update mechanishm on mongodb 3.0.1. from MMAP to WiredTiger described here: http://docs.mongodb.org/manual/release-notes/3.0-upgrade/#change-replica-set-storage-engine-to-wiredtiger |
||||||||||||||||||||
| Sprint: | RPL 1 04/03/15, RPL 2 04/24/15 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
| Comments |
| Comment by Githook User [ 07/Jul/15 ] | |||||||||||||||
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: (cherry picked from commit 57232d88b869b0741d95998f8ed09a96b2e7a1bc) | |||||||||||||||
| Comment by Scott Hernandez (Inactive) [ 02/Jun/15 ] | |||||||||||||||
|
Backport Notes:
Alternative: | |||||||||||||||
| Comment by Githook User [ 01/Jun/15 ] | |||||||||||||||
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: Revert " This reverts commit 411802f844fa09bedb4f80d14e76bb94d2e3cae0. | |||||||||||||||
| Comment by Githook User [ 01/Jun/15 ] | |||||||||||||||
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: (cherry picked from commit 57232d88b869b0741d95998f8ed09a96b2e7a1bc) | |||||||||||||||
| Comment by Githook User [ 23/Apr/15 ] | |||||||||||||||
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: | |||||||||||||||
| Comment by Scott Hernandez (Inactive) [ 23/Mar/15 ] | |||||||||||||||
|
sjoerdmulder Thanks for filing the issue so we can address this in initial sync. | |||||||||||||||
| Comment by Sjoerd Mulder [ 23/Mar/15 ] | |||||||||||||||
|
Update: second time the initial sync replication did succeed, so i'm not sure if this can be reproduced easily | |||||||||||||||
| Comment by Andy Schwerin [ 23/Mar/15 ] | |||||||||||||||
|
My guess is that Sync::shouldRetry is throwing WriteConflictException in multiInitialSyncApply. SyncTail::syncApply handles WCE internally, which is probably what Sync::shouldRetry ought to do, as well. |