Triage is planning on relying on log messages for all index inconsistencies to get around the 16MB document size limit when it comes to validation results supplied to them by Cloud. They are specifically hoping to rely on logging as opposed to any messages stored in the validate command response object (in the errors array, for example, as is currently done).

Currently, it appears that if we encounter indexes that have inconsistencies, but that we do not have the memory available to check their specific inconsistencies (as determined by maxValidateMemoryUsageMB), we do not not log any information about these indexes and their inconsistencies (it looks like we 'zero out', or basically mark as valid, any indexes that we do not have the space to look into here).

This ticket would investigate whether we can add any kind logging for indexes that we do not have the memory to investigate in the second phase of index validation (for example, whether the inconsistency was an extra index or a missing index). If we cannot, we could log a message indicating that an index had an inconsistency but that we do not have the memory to investigate what kind of inconsistency it was (currently we add a message to the errors array of the validate command response object.