[DOCS-3288] Documents in Capped Collections should not be modified Created: 28/Apr/14 Updated: 16/Mar/15 Due: 28/May/14 Resolved: 18/Jun/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | mongodb-2.6 |
| Fix Version/s: | v1.3.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Ryder (Inactive) | Assignee: | Tim Slavin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 9 years, 35 weeks ago | ||||||||||||
| Description |
|
http://docs.mongodb.org/manual/core/capped-collections/#recommendations-and-restrictions
See If a document in a capped collection is updated to be smaller, and then a secondary is re-sync'ed from it, the secondary will replicate (and allocate) based on the current smaller size. If the primary then receives an update which grows the document back to the original size (perfectly safe according to the above quote), the primary will accept the update, but the secondary will die with a fatal assertion. A document in a capped collection which was shrunk from it's original size is a landmine. We should give a warning about this problem. See |
| Comments |
| Comment by Githook User [ 18/Jun/14 ] |
|
Author: {u'username': u'TimSlavinMongoDB', u'name': u'Tim Slavin (MongoDB)', u'email': u'tim.slavin@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |
| Comment by Asya Kamsky [ 28/Apr/14 ] |
|
Why don't we just say "You can only make in-place updates" instead of "You can update documents in a collection after inserting them." |