[SERVER-10927] if a replicaset member goes down during a $out we are left with an inconsistent state Created: 26/Sep/13 Updated: 11/Jul/16 Resolved: 07/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | 2.5.2 |
| Fix Version/s: | 2.5.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Dannenberg | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
If you kill a server during $out you well end up in one of two bad states. If it's the primary you kill, the secondaries are left with the tmp collections. If it's a secondary you kill, that secondary will drop the tmp collection when it restarts and then continue building the tmp collection as it reads the primary's oplog. As a result, the entries written before the reboot are absent from the output collection once the aggregation has finished. |
| Comments |
| Comment by auto [ 11/Oct/13 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Test is for |
| Comment by auto [ 10/Oct/13 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by auto [ 09/Oct/13 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Fixes a race condition causing some builders to fail |
| Comment by auto [ 07/Oct/13 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Non-replicated hosts still drop temp collections on startup. This is |