It's possible for a waiting isMaster request to time out waiting for a topology change here, then for the server to enter quiesce mode before the request constructs a response here. In this case, the response will fail to indicate that the server is in quiesce mode, but it will include the new topology version. A solution would be to have _makeIsMasterResponse() check for quiesce mode.