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

Capped collection size is adjusted during rollback while FCV downgrading from 7.0 to 6.0

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • 0

      This can lead to the node that went through rollback reporting a different capped collection maxSize than nodes in the cluster that do not rollback.

      How we get there: 

      This is affected by refreshing the in-memory FCV value to reflect the post rollback state.

            Assignee:
            Unassigned Unassigned
            Reporter:
            shinyee.tan@mongodb.com Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: