We would like to add a new command argument that specifies how long a client is willing to wait for data to become majority committed when doing a speculative majority read. This is primarily to work around the fact that getMore commands on tailable, awaitData cursors do not use maxTimeMS as a global command timeout. They instead use it as the amount of time to wait for new inserts before returning to the client. Since speculative majority waiting may happen after batch generation, there is no way currently to specify a time limit on speculative majority waiting in this case. The goal is to address this issue with a new parameter; something analogous to the wtimeout parameter of write concern.