mongodb set feature compatibility to 3.4 failNot able to access a database on shard mongodb clusterMongoDB...
Misplaced tyre lever - alternatives?
Sometimes a banana is just a banana
Reason why dimensional travelling would be restricted
Did Amazon pay $0 in taxes last year?
Has Wakanda ever accepted refugees?
GPL code private and stolen
If nine coins are tossed, what is the probability that the number of heads is even?
Correct physics behind the colors on CD (compact disc)?
A bug in Excel? Conditional formatting for marking duplicates also highlights unique value
Why won't the strings command stop?
1970s scifi/horror novel where protagonist is used by a crablike creature to feed its larvae, goes mad, and is defeated by retraumatising him
PTIJ: Aharon, King of Egypt
Where is this quote about overcoming the impossible said in "Interstellar"?
Can I solder 12/2 Romex to extend wire 5 ft?
Why do phishing e-mails use faked e-mail addresses instead of the real one?
Formatting a table to look nice
Can we carry rice to Japan?
Create chunks from an array
Rationale to prefer local variables over instance variables?
Is there a full canon version of Tyrion's jackass/honeycomb joke?
Is there a way to find out the age of climbing ropes?
Why would the IRS ask for birth certificates or even audit a small tax return?
Would the melodic leap of the opening phrase of Mozart's K545 be considered dissonant?
PTIJ: What’s wrong with eating meat and couscous?
mongodb set feature compatibility to 3.4 fail
Not able to access a database on shard mongodb clusterMongoDB cluster setupCould not add Replica Set to MongoDB Shardmongodump: are 4 shards with total datasize 575 GB consider a Small Sharded Cluster?“Unexpected Error” occurs when using Ops Manager ProfilerMongoDB config replica failed connection after a few days runningMongo shell 3.2 has different results on sh.isBalancerRunning() as mongo shell 3.4Authenticate MongoDB shard cluster in Docker swarmIssue with MongoDB Replication SetNot authorized on admin to execute command mongoDB: Atlas M0 Free Tier cluster
I want to enable the features of my Mongodb 3.4 after upgrading. I have sharded cluster enviroment And after I ran the commands:
use admin
db.adminCommand ({setFeatureCompatibilityVersion: "3.4"})
In mongos instance I got the following output:
{"ok": 1}
But when I try to check with it succeeded with command:
db.adminCommand ({getParameter: 1, featureCompatibilityVersion: 1})
I get the following output:
{"ok": 0, "errmsg": "no option found to get"}
And when I check in ops manager I see that the command did not work
mongodb-3.2 mongodb-3.4
asked May 8 '18 at 11:05
thecollectorthecollector
61
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I want to enable the features of my Mongodb 3.4 after upgrading. I have sharded cluster enviroment And after I ran the commands:
use admin
db.adminCommand ({setFeatureCompatibilityVersion: "3.4"})
In mongos instance I got the following output:
{"ok": 1}
But when I try to check with it succeeded with command:
db.adminCommand ({getParameter: 1, featureCompatibilityVersion: 1})
I get the following output:
{"ok": 0, "errmsg": "no option found to get"}
And when I check in ops manager I see that the command did not work
mongodb-3.2 mongodb-3.4
asked May 8 '18 at 11:05
thecollectorthecollector
61
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Anddb.serverStatus().versioncommand gives you3.4.xanswer?
– JJussi
May 9 '18 at 14:35
add a comment |
I want to enable the features of my Mongodb 3.4 after upgrading. I have sharded cluster enviroment And after I ran the commands:
use admin
db.adminCommand ({setFeatureCompatibilityVersion: "3.4"})
In mongos instance I got the following output:
{"ok": 1}
But when I try to check with it succeeded with command:
db.adminCommand ({getParameter: 1, featureCompatibilityVersion: 1})
I get the following output:
{"ok": 0, "errmsg": "no option found to get"}
And when I check in ops manager I see that the command did not work
mongodb-3.2 mongodb-3.4
asked May 8 '18 at 11:05
thecollectorthecollector
61
I want to enable the features of my Mongodb 3.4 after upgrading. I have sharded cluster enviroment And after I ran the commands:
use admin
db.adminCommand ({setFeatureCompatibilityVersion: "3.4"})
In mongos instance I got the following output:
{"ok": 1}
But when I try to check with it succeeded with command:
db.adminCommand ({getParameter: 1, featureCompatibilityVersion: 1})
I get the following output:
{"ok": 0, "errmsg": "no option found to get"}
And when I check in ops manager I see that the command did not work
mongodb-3.2 mongodb-3.4
mongodb-3.2 mongodb-3.4
asked May 8 '18 at 11:05
thecollectorthecollector
61
asked May 8 '18 at 11:05
thecollectorthecollector
61
asked May 8 '18 at 11:05
thecollectorthecollector
61
asked May 8 '18 at 11:05
thecollectorthecollector
61
asked May 8 '18 at 11:05
thecollectorthecollector
61
61
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Anddb.serverStatus().versioncommand gives you3.4.xanswer?
– JJussi
May 9 '18 at 14:35
add a comment |
Anddb.serverStatus().versioncommand gives you3.4.xanswer?
– JJussi
May 9 '18 at 14:35
And
db.serverStatus().version command gives you 3.4.x answer?– JJussi
May 9 '18 at 14:35
And
db.serverStatus().version command gives you 3.4.x answer?– JJussi
May 9 '18 at 14:35
add a comment |
1 Answer
1
active
oldest
votes
You probably ran your command
db.adminCommand ({getParameter: 1, featureCompatibilityVersion: 1})
on a mongos instance. The documentation states in this case:
The operation is undefined on the mongos instances. For a sharded cluster that has access control enabled, to run the command against a member of the shard replica set, you must connect to the member as a shard local user.
When you connect to a mongod instead, the command should work as expected.
answered Jan 30 at 13:40
Jan GassenJan Gassen
1084
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f206135%2fmongodb-set-feature-compatibility-to-3-4-fail%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You probably ran your command
db.adminCommand ({getParameter: 1, featureCompatibilityVersion: 1})
on a mongos instance. The documentation states in this case:
The operation is undefined on the mongos instances. For a sharded cluster that has access control enabled, to run the command against a member of the shard replica set, you must connect to the member as a shard local user.
When you connect to a mongod instead, the command should work as expected.
answered Jan 30 at 13:40
Jan GassenJan Gassen
1084
add a comment |
You probably ran your command
db.adminCommand ({getParameter: 1, featureCompatibilityVersion: 1})
on a mongos instance. The documentation states in this case:
The operation is undefined on the mongos instances. For a sharded cluster that has access control enabled, to run the command against a member of the shard replica set, you must connect to the member as a shard local user.
When you connect to a mongod instead, the command should work as expected.
answered Jan 30 at 13:40
Jan GassenJan Gassen
1084
add a comment |
You probably ran your command
db.adminCommand ({getParameter: 1, featureCompatibilityVersion: 1})
on a mongos instance. The documentation states in this case:
The operation is undefined on the mongos instances. For a sharded cluster that has access control enabled, to run the command against a member of the shard replica set, you must connect to the member as a shard local user.
When you connect to a mongod instead, the command should work as expected.
answered Jan 30 at 13:40
Jan GassenJan Gassen
1084
You probably ran your command
db.adminCommand ({getParameter: 1, featureCompatibilityVersion: 1})
on a mongos instance. The documentation states in this case:
The operation is undefined on the mongos instances. For a sharded cluster that has access control enabled, to run the command against a member of the shard replica set, you must connect to the member as a shard local user.
When you connect to a mongod instead, the command should work as expected.
answered Jan 30 at 13:40
Jan GassenJan Gassen
1084
answered Jan 30 at 13:40
Jan GassenJan Gassen
1084
answered Jan 30 at 13:40
Jan GassenJan Gassen
1084
answered Jan 30 at 13:40
Jan GassenJan Gassen
1084
1084
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f206135%2fmongodb-set-feature-compatibility-to-3-4-fail%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
And
db.serverStatus().versioncommand gives you3.4.xanswer?– JJussi
May 9 '18 at 14:35