[SERVER-19212] New indexes shouldn't be usable until they are in the committed view Created: 29/Jun/15 Updated: 02/Aug/18 Resolved: 12/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.7 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Should probably make index builds block until that point as well. |
| Comments |
| Comment by Githook User [ 12/Aug/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: This ensures that when a w:majority write that makes a new collection |
| Comment by Githook User [ 12/Aug/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Reading from a collection will error out if the snapshot used by the query is New indexes do not cause reads to fail, but reads cannot use the new indexes |
| Comment by Githook User [ 05/Aug/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by Githook User [ 05/Aug/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Allows distinguishing snapshots created with the same OpTime as needed for |