[SERVER-24127] Server can abort when creating capped collection with invalid size Created: 10/May/16  Updated: 19/Nov/16  Resolved: 30/Sep/16

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 3.0.0
Fix Version/s: 3.4.0-rc0

Type: Bug Priority: Major - P3
Reporter: Kamran K. Assignee: Geert Bosch
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Integration 2016-09-19, Integration 2016-10-10
Participants:
Linked BF Score: 0

 Description   

This bug affects versions 3.0+.

WiredTiger exhibits an invariant failure:

2016-05-10T16:49:21.101-0400 I -        [conn2] Invariant failure _cappedMaxSize > 0 src/mongo/db/storage/wiredtiger/wiredtiger_record_store.cpp 825
2016-05-10T16:49:21.101-0400 I -        [conn2] 
 
***aborting after invariant() failure

mmapv1 exhibits a fatal assertion:

2016-05-10T16:48:14.184-0400 I -        [conn1] Fatal assertion 18523 BadValue: size has to be >= 0
2016-05-10T16:48:14.184-0400 I -        [conn1] 
 
***aborting after fassert() failure



 Comments   
Comment by Githook User [ 30/Sep/16 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-24127 Avoid overflow rounding up the capped size
Branch: master
https://github.com/mongodb/mongo/commit/94e64d51137d66c3af56bc1d00a5c5ec77c8e55e

Generated at Thu Feb 08 04:05:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.