[SERVER-19015] Dissallow convertToCapped on capped collections Created: 17/Jun/15  Updated: 14/Mar/17  Resolved: 19/Jan/16

Status: Closed
Project: Core Server
Component/s: Admin, Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Adam Midvidy
Resolution: Won't Fix Votes: 0
Labels: fuzzer-blacklist, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-8971 Dissallow convertToCapped on capped c... Closed
Related
Backwards Compatibility: Minor Change
Sprint: Integration F (02/01/16)
Participants:
Linked BF Score: 0

 Description   

This causes potential problems since:

  • Secondary indexes aren't created on the new collection
  • A DB lock is taken to copy the docs to the new collection
  • Using this with "system.profile" causes problems

So instead we should return an error that the collection is already capped and the operation did not complete.



 Comments   
Comment by Adam Midvidy [ 19/Jan/16 ]

Closing as WONTFIX due to 2 issues:

(1): it will lead to a crash during upgrade if a convertToCapped command is
issued against a 3.2 secondary and replicated to a 3.4 primary.
(2): it breaks the ability of users to resize capped collections. Ideally we
would support this in collMod, but support isn't there now. MMS also depends on this functionality.

Generated at Thu Feb 08 03:49:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.