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

RS secondary node correct state during compaction

    XMLWordPrintable

    Details

    • Type: Question
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Community Answered
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Hi there, I have some questions about compaction procedure on v4.4.
      As it's mentioned here https://docs.mongodb.com/v4.4/reference/command/compact/ 
      "Starting in v4.4, compact does not change the run state of the secondary, and clients may continue to read from the secondary during the compaction operation.", so we expected the same behavior during our compaction procedure running on v4.4.4.
      But our secondary did change its state to RECOVERING.

      Just to clarify behavior I decided to double-check all the compaction-related tasks and stumbled upon this one - https://jira.mongodb.org/browse/SERVER-54445.

      Quote - "We didn't change the behavior of setting maintenance mode on secondary nodes. We should make the documentation clearer about this. We have DOCS-14122 to clarify this behavior.", but there are no updates since February 2021.

      So what's the right behavior for secondary nodes of the RS during compaction?
      Are you planning to implement seamless compaction, so secondaries would stay secondaries during operation, or it's just documentation lack and the current recovery-switching behavior is correct?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dmitry.agranat Dmitry Agranat
              Reporter:
              haltandcatchfire91@gmail.com Basil Markov
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: