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

Prohibit setting the 'expireAfterSecond' field if the change collection mode is not active

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • QE 2022-09-19, QE 2022-10-03

      The expireAfterSeconds change streams parameter will be available to the setClusterParameter command in version 6.1. The CWC currently does not support gating configuration via FCVs as such the user can set this configuration in version 6.1. While rolling the expireAfterSeconds configuration in v6.1 should not be an issue in the field, we should still ensure that this parameter can only be used after the PM-2334 is enabled. This is in accordance with the CWC recommendation.

      PM-2334 project will potentially be released at/after v6.2. We should continue to block setting this parameter until the feature flag/fcv_6.2 is enabled.

       

      As part of this ticket, we should also ensure that pre-images.expireAfterSeconds CWC parameter cannot be set in the serverless, this is because in the serverless we will use changeStreams.expireAfterSeconds to set retention time for the change collection and the pre-images collection.

            Assignee:
            romans.kasperovics@mongodb.com Romans Kasperovics
            Reporter:
            rishab.joshi@mongodb.com Rishab Joshi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: