My expectation was that if I sent an imaster request with the exhaustAllowed bit set and a requestId of 42, that subsequent responses would indicate a responseTo: 42 with the moreToCome bit set. Instead, I'm seeing that moreToCome is set, but the responseTo field changes on each response. My guess is that the exhaust support for awaitable ismaster is using an internal mechanism to simulate getMore requests.

Is it possible to maintain the original requestId for the lifetime of the request in these cases? Otherwise, a driver will be required to develop custom logic only for this command.