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

Don't check index key size on the secondary

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.1.3
    • Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-08-27

    Description

      It's possible to have a scenario that while the secondary is building index at background, the FCV is set from 4.2 to 4.0. In that case,the index key size check should still be bypassed because long index keys already exist on the primary. Secondaries should unconditionally accept large index keys.

      Attachments

        Issue Links

          Activity

            People

              xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
              xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: