Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

mongodb cant set 3.4 features after upgrade from 3.2

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.

Environment

None

Activity

Igor Solodovnikov 
May 9, 2018 at 1:10 PM

Hi,

yes, Tomislav is right - getParameter for feature compatibility version is not supported on mongos instances. This is documented here: https://docs.mongodb.com/v3.4/reference/command/setFeatureCompatibilityVersion/
See the note at the end saying "The operation is undefined on the mongos instances."

Tomislav Plavcic 
May 4, 2018 at 7:31 AM

Hi,

mongos doesn't seem to support getting that parameter. It can be set from mongos and it will upgrade replica sets/shards to new featureCompatibilityVersion but you can only get that parameter from mongod's (config, data servers). So I suggest to just connect to config replica set and check there.

Also make sure you followed upgrade instructions from here: https://docs.mongodb.com/v3.4/release-notes/3.4-upgrade-sharded-cluster/

Not a Bug

Details

Assignee

Reporter

Labels

Time tracking

20m logged

Affects versions

Priority

Created May 3, 2018 at 3:46 PM
Updated March 6, 2024 at 5:13 PM
Resolved May 3, 2018 at 3:46 PM