calling serverStatus() on mongodb replicas returns the same information











up vote
1
down vote

favorite












Calling db.runCommand( { serverStatus: 1 } ) on mongodb replicas, one would expect to get different metrics from the primary, eg number of connections, replications operations, etc.



However, no matter which node I query, I get the exact same result.



How do I accurately get per node metrics, like connections? It seems like they are being fetched from the primary instead.










share|improve this question




























    up vote
    1
    down vote

    favorite












    Calling db.runCommand( { serverStatus: 1 } ) on mongodb replicas, one would expect to get different metrics from the primary, eg number of connections, replications operations, etc.



    However, no matter which node I query, I get the exact same result.



    How do I accurately get per node metrics, like connections? It seems like they are being fetched from the primary instead.










    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      Calling db.runCommand( { serverStatus: 1 } ) on mongodb replicas, one would expect to get different metrics from the primary, eg number of connections, replications operations, etc.



      However, no matter which node I query, I get the exact same result.



      How do I accurately get per node metrics, like connections? It seems like they are being fetched from the primary instead.










      share|improve this question















      Calling db.runCommand( { serverStatus: 1 } ) on mongodb replicas, one would expect to get different metrics from the primary, eg number of connections, replications operations, etc.



      However, no matter which node I query, I get the exact same result.



      How do I accurately get per node metrics, like connections? It seems like they are being fetched from the primary instead.







      mongodb






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 10 at 4:14









      lgwilliams

      129211




      129211










      asked Nov 9 at 20:10









      pdeva

      12.3k36110141




      12.3k36110141
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          i found the solution. it was the driver. it was passing information to the primary. i had to modify the connect string to make it talk directly to the replica only.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            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',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            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%2fstackoverflow.com%2fquestions%2f53232678%2fcalling-serverstatus-on-mongodb-replicas-returns-the-same-information%23new-answer', 'question_page');
            }
            );

            Post as a guest
































            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            i found the solution. it was the driver. it was passing information to the primary. i had to modify the connect string to make it talk directly to the replica only.






            share|improve this answer

























              up vote
              0
              down vote













              i found the solution. it was the driver. it was passing information to the primary. i had to modify the connect string to make it talk directly to the replica only.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                i found the solution. it was the driver. it was passing information to the primary. i had to modify the connect string to make it talk directly to the replica only.






                share|improve this answer












                i found the solution. it was the driver. it was passing information to the primary. i had to modify the connect string to make it talk directly to the replica only.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 10 at 14:36









                pdeva

                12.3k36110141




                12.3k36110141






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53232678%2fcalling-serverstatus-on-mongodb-replicas-returns-the-same-information%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest




















































































                    Popular posts from this blog

                    Xamarin.iOS Cant Deploy on Iphone

                    Glorious Revolution

                    Dulmage-Mendelsohn matrix decomposition in Python