Improve tassert logging in Change Stream events.

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently we have assertions around what oplog events should reach change stream transformer. For example:

      https://github.com/mongodb/mongo/blob/b61c79e53b8fd9ae3b2c86a5ba6be6e19d8e308b/src/mongo/db/pipeline/change_stream_event_transform.cpp#L499

       

      However, if an oplog entry leaks through (due to a bug, probably) a resulting assert message will contain very little information and will be hard to debug.

      We should log the offending oplog entry type (and maybe the whole entry, but redacted) to make such errors easier to debug.

            Assignee:
            Unassigned
            Reporter:
            Ivan Fefer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: