[SERVER-24739] Unhandled duration_cast exception in DataFileSync::run can terminate server Created: 22/Jun/16  Updated: 06/Dec/17  Resolved: 29/Nov/16

Status: Closed
Project: Core Server
Component/s: MMAPv1
Affects Version/s: 3.3.8
Fix Version/s: 3.5.1

Type: Bug Priority: Major - P3
Reporter: Kamran K. Assignee: Daniel Gottlieb (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-24104 Replace std::duration types with impl... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage 2016-12-12
Participants:
Linked BF Score: 0

 Description   

It's possible for the server to terminate with an unhandled duration_cast exception if an invalid syncdelay value is specified:

d20000| 2016-06-22T17:25:51.587-0400 E COMMAND  [DataFileSync] backgroundjob DataFileSync exception: Overflow casting from a lower-precision duration to a higher-precision duration
d20000| 2016-06-22T17:25:51.588-0400 F -        [DataFileSync] terminate() called. An exception is active; attempting to gather more information
d20000| 2016-06-22T17:25:51.590-0400 F -        [DataFileSync] DBException::toString(): 159 Overflow casting from a lower-precision duration to a higher-precision duration
d20000| Actual exception type: mongo::UserException

This bug seems to have been introduced after 3.3.6.



 Comments   
Comment by Githook User [ 29/Nov/16 ]

Author:

{u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}

Message: SERVER-24739: Validate syncdelay at startup and on setParameter
Branch: master
https://github.com/mongodb/mongo/commit/df8ee2e1ffcf24ff1a871ddd0ca1a68d778c77bf

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