In our docs, we claim that replSetReconfig allows an optional maxTimeMS parameter that may fail reconfig if it takes longer than the specified value. However, from code inspection, it looks like we never parse this field, and our oplog commitment write concern always has a wtimeout of infinite. We should investigate if this is intentional, and either update the docs or correct the code to make use of maxTimeMS