Don't check index key size on the secondary

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.3
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-08-27
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Xiangyu Yao (Inactive)
            Reporter:
            Xiangyu Yao (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: