[SERVER-27146] Enforce maxStalenessSeconds >= 90 Created: 21/Nov/16  Updated: 05/Apr/17  Resolved: 12/Dec/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.4.0-rc4
Fix Version/s: 3.4.2, 3.5.1

Type: Improvement Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Misha Tyulenev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: Sharding 2016-12-12, Sharding 2017-01-02
Participants:

 Description   

Changes to max staleness spec:

The $readPreference option "maxStalenessSeconds" is no longer allowed to be double, it's once again only int32 or int64. (This change can be put off, need not block 3.4.)

The minimum is now 90 seconds. (3.4 blocker.)

See the "mongos tests" section here:

https://github.com/mongodb/specifications/blob/master/source/max-staleness/max-staleness-tests.rst#mongos

cc schwerin misha.tyulenev



 Comments   
Comment by Misha Tyulenev [ 28/Dec/16 ]

Backported as part of SERVER-26927
Author:

{u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}

Message: SERVER-26927 support integer values for maxStalenessSeconds
(cherry picked from commit 3878fd8993b361207a853b8db11a1a3b484ea837)
Branch: v3.4
https://github.com/mongodb/mongo/commit/2385fd34587de3b75c4205f45821b23cecb79dce

Comment by Misha Tyulenev [ 13/Dec/16 ]

Fixed as part of SERVER-26927:

Author:{u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}
Message: SERVER-26927 support integer values for maxStalenessSeconds
Branch: master
https://github.com/mongodb/mongo/commit/3878fd8993b361207a853b8db11a1a3b484ea837

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