Uploaded image for project: 'Percona Server for MongoDB'
  1. Percona Server for MongoDB
  2. PSMDB-213

mongodb cant set 3.4 features after upgrade from 3.2

    Details

    • Type: Bug
    • Status: Done
    • Priority: Medium
    • Resolution: Invalid
    • Affects Version/s: 3.2.19-3.10
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      I upgraded my Sharded Cluater to version 3.4 with RocksDB storage engine. The problem is when I run the command:
      db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )

      on the mongos instance I got:
      { "ok" : 1 }
      But when I want to check if it really was done with the command:
       db_.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 }_I get the answer:
      { "ok" : 0, "errmsg" : "no option found to get" }And it did not seem to work.

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                shlomo156 Shlomo Prayev
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 20 minutes
                  20m