In a few cases, we are seeing max document size errors when querying mongo. The only way we have found to resolve this is to manually change the cursor batch size for the failing queries. We are having to calculate this value ourselves based on our own knowledge of the expected maximum document size for particular collections. We would expect that this would be handled automatically in the driver (or server?)