When the driver pins a thread to a socket using DB.requestStart(), it should remember the read preference used for the first read. If a subsequent read has a different read preference, unpin the member and start the member-selection process from scratch and rebind the thread to a different socket.

Currently, the driver ignores changes to read preference on queries performed within DB.requestStart/requestEnd boundaries.