In theory the primary could know that secondaries are behind to much to possibly finish the current write in the timeout window specified by the caller of the getLastError command, and not wait to time out. this would likely improve stability of client apps as their entire conn pools would likely saturate if cluster is normally super responsive and then suddenly high timeout waits occur.