mongodb set feature compatibility to 3.4 failNot able to access a database on shard mongodb clusterMongoDB...

Why would the IRS ask for birth certificates or even audit a small tax return?

Lock enemy's y-axis when using Vector3.MoveTowards to follow the player

Why are special aircraft used for the carriers in the United States Navy?

Difference between 'stomach' and 'uterus'

Can metaphors be used for other purposes than for stylistic effect and to form an allegory?

What does each site of a vanilla 9.1 installation do?

Practical reasons to have both a large police force and bounty hunting network?

How to use math.log10 function on whole pandas dataframe

Understanding the template

Correct physics behind the colors on CD (compact disc)?

Draw bounding region by list of points

Specific Chinese carabiner QA?

If there are any 3nion, 5nion, 7nion, 9nion, 10nion, etc.

Can an earth elemental drown/bury its opponent underground using earth glide?

How can I be pwned if I'm not registered on the compromised site?

Is there a frame of reference in which I was born before I was conceived?

How can I handle a player who pre-plans arguments about my rulings on RAW?

Quitting employee has privileged access to critical information

Reason why dimensional travelling would be restricted

Rationale to prefer local variables over instance variables?

When to use mean vs median

GPL code private and stolen

Sometimes a banana is just a banana

The need of reserving one's ability in job interviews



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













1















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










share|improve this question














bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • And db.serverStatus().version command gives you 3.4.x answer?

    – JJussi
    May 9 '18 at 14:35
















1















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










share|improve this question














bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • And db.serverStatus().version command gives you 3.4.x answer?

    – JJussi
    May 9 '18 at 14:35














1












1








1








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










share|improve this question














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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 8 '18 at 11:05









thecollectorthecollector

61




61





bumped to the homepage by Community 5 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 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • 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

















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










1 Answer
1






active

oldest

votes


















0














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.






share|improve this answer























    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
    });


    }
    });














    draft saved

    draft discarded


















    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









    0














    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.






    share|improve this answer




























      0














      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.






      share|improve this answer


























        0












        0








        0







        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.






        share|improve this answer













        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.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 30 at 13:40









        Jan GassenJan Gassen

        1084




        1084






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            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





















































            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







            Popular posts from this blog

            Armoriale delle famiglie italiane (Car) Indice Armi | Bibliografia | Menu di navigazioneBlasone...

            Why does this relation fail symmetry and transitivity properties?Properties of Relations. Reflexive,...

            why typing a variable (or expression) prints the value to stdout?Calling a function of a module by using its...