Uploaded image for project: 'MongoDB Database Tools'
  1. MongoDB Database Tools
  2. TOOLS-598

mongostat --discover requires all members be up during first sample period

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.0.0-rc6
    • 3.0.0-rc8
    • mongostat
    • None
    • Observed on OS X, Linux x64
    • Not Needed

    Description

      To reproduce:

      1.) Start up a vanilla 3 node set on say ports 2400, 2401, 2402.
      2.) $ mongostat --port 2400 --discover 5
      3.) All nodes are discovered and report stats - everything's happy
      4.) Shutdown node on port 2401.
      5.) mongostat continues, simply reports "no reachable servers" for the down node - still fine.
      6.) now with the 2401 member still down, stop mongostat and restart with same command as step #2.

      $ mongostat --port 2400 --discover 5
      2015-01-27T22:37:31.561-0500	Failed: error connecting to db server: no reachable servers
      $

      So, if any node is down when first connecting, the whole command fails instead of continuing on with the 2 good nodes like in step #5, which is what I would expect.

      Attachments

        Activity

          People

            kyle.erf Kyle Erf
            john.morales@mongodb.com John Morales
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: