Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
Cluster Scalability
Description
We currently hardcode these two (kWriteConcernTimeoutSharding{60} and kWriteConcernTimeoutUserCommand{60} ) values at 60 seconds each. In some cases, it might be desirable to modify these values, so they should be configurable via a server parameter instead.
Attachments
Issue Links
- is related to
-
SERVER-84439 appendMajorityWriteConcern should only override wtimeout if it is non-zero
-
- Open
-