Better logging for movePrimary/moveChunk when error occurs

XMLWordPrintableJSON

    • Fully Compatible
    • Sharding 2020-05-04
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We currently use the uassertStatusOKWithWarning to log errors that occurred when running moveChunk/movePrimary:

      https://github.com/mongodb/mongo/blob/r4.3.2/src/mongo/db/s/move_chunk_command.cpp#L229
      https://github.com/mongodb/mongo/blob/r4.3.2/src/mongo/db/s/move_primary_command.cpp#L162

      However, these only catches cases when the error is propagated via a returned status. There are a few cases where we use uasserts inside these calls and they won't show up in the log default setting unless it is verbose enough to show assertion messages.

            Assignee:
            Pierlauro Sciarelli
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: