The code for tracking the optime of the last write operation, specifically when that operation was index creation, has a bug on mongos that is exposed when the createIndexes command was forwarded to one or more shards using a new connection. Specifically, sometimes mongos will mistakenly believe that the optime of the createIndexes operation one or more shards was (0|0), causing waits for write concern >= w:2 to return too early.