Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-84324

replSetGetStatus could asserts silently if initialSyncStatus is too large.

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Replication

    Description

      I think this client is hitting the case that initialSyncStatus is too large that it can fit in BSON obj but it fails when it is being added to replSetGetStatus response (here).

      We already fixed too large initialSyncStatus by having another minimal version of initialSyncStatus (SERVER-31995), So we should also append that minimal versions if replSetGetStatus grows over 16mb.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            m.maher@mongodb.com Moustafa Maher
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: