-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2020-01-27, Repl 2020-02-10
-
95
We currently parse the wTimeout field of a writeConcern object using numberInt(). However, the documentation for numberInt() states that we will get undefined behavior for cases like when given a double too large/small to be expressed as an int or a double that is NaN. The documentation suggests using safeNumberLong() instead.
- is related to
-
SERVER-70360 Do not allow extremely large write concern wTimeout values
- Closed
- related to
-
SERVER-45584 Validate writeConcern.w
- Closed