mixing 1.8.3 and 2.0.0 in a replica set will cause 1.8.3 cannot use it's indexes

XMLWordPrintableJSON

    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. set up a new replica set on a 2.0.0 server
      2. insert some data and create some indexes on them
      3. add a 1.8.3 SECONDARY and a ARBITER and wait for the resync to complete
      4. stop the PRIMARY, wait for the 1.8.3 SECONDARY to became PRIMARY
      5. do some queries on the new 1.8.3 PRIMARY. the server cannot use the indexes.

              Assignee:
              Unassigned
              Reporter:
              Liu Qishuai
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: