[DOCS-15777] [SERVER] wTimeout values on large write concerns Created: 05/Dec/22  Updated: 13/Nov/23  Resolved: 13/Jul/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 6.3.0-rc0, 6.0.5, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Nick Lopez Del Pino (Inactive)
Resolution: Done Votes: 0
Labels: server-docs-bug-bash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backported by DOCS-15833 [BACKPORT] [v6.0] Do not allow extrem... Closed
Documented
documents SERVER-70360 Do not allow extremely large write co... Closed
Participants:
Days since reply: 1 year, 2 weeks, 3 days ago

 Description   

Original title:
Investigate changes in SERVER-70360: Do not allow extremely large write concern wTimeout values

-------

Original Downstream Change Summary

We've been pretty vague about what the value of wtimeout can be, but now we should explicitly mention it has to be an int32. (We actually only supported that until somewhat recently, but we never documented any of this).

Description of Linked Ticket

We allow 64-bit values for wTimeout. Timeouts which are very large don't make a lot of sense and we should reject them.



 Comments   
Comment by Education Bot [ 23/Jan/23 ]

Fix Version updated for upstream SERVER-70360:
6.3.0-rc0, 6.0.5

Comment by Education Bot [ 05/Dec/22 ]

Fix Version updated for upstream SERVER-70360:
6.3.0-rc0

Generated at Thu Feb 08 08:13:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.