Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-7836

Clarify mongotop usage with secondaries in replica sets

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.8, 3.2.7
    • Component/s: tools
    • Labels:
      None
    • Last comment by Customer:
      true

      Description

      The mongotop --host documentation notes the syntax for connecting to a replica set. Afterwards it states:

      You can always connect directly to a single MongoDB instance by specifying the host and port number directly.

      I find this information ambiguous. Especially considering this comment in TOOLS-506, I believe that a "single MongoDB instance" includes secondaries in this context (therefore mongotop should be able to connect to them if not using the replica set syntax). However, others believe that mongotop can only connect to the primary of a replica set. Output from the primary is the case when using the replica set syntax but not the behavior I would expect with the "single MongoDB instance" syntax based on my understanding (pending the results of TOOLS-1166).

      The documentation should be updated to clarify what a "single MongoDB instance" means as it is leading to different interpretations of how the tool can be used with members (secondaries) of a replica set.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              isabella.siu Isabella Siu (Inactive)
              Reporter:
              christopher.harris Christopher Harris
              Participants:
              Last commenter:
              Isabella Siu Isabella Siu (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                2 years, 41 weeks, 1 day ago
                Date of 1st Reply: