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

Tutorial for setting up a replica set on Azure has many errors

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None

    Description

      The tutorial here has many errors. I'm listing the ones I have found here and will update as I resolve them, but potentially the whole document needs review.

      • Set up Affinity Group - Click 'Preview' does not exist anymore, now to get to previous portal, click on your user name (top right corner)
      • Instance 2 step 3 has Virtual Machine name as "mongodbrs1" (same as instance 1)
      • Instance 2 step 4 has the same DNS name as the previous instance, wouldn't be allowed in the wizard.
      • Instance 2 step 4 has a screenshot indicating that the user should use "connect to existing virtual machine" rather than "standalone virtual machine"
      • We change the default ports for SSH on two instances, unsure why.
      • Underscore in Install MongoDB step 2 (_/etc/yum.repos.d...)
      • Bad Yum Repo (has square brackets around the URL)
      • Configure the replica set - Config we give is completely wrong:
        • has id instead of _id
        • has "\" on each line for the members (presumably to escape the braces, which is not required)
        • id for all members is 0 (and also not _id)
        • DNS name for all hosts is "mongodbrs" (indicating all three members would be on the same node, as opposed to what we have set up)
      • Summary indicates you could connect to "mongodb://mongodbrs.cloudapp.net:27018, mongodbrs.cloudapp.net:27019, mongodbrs.cloudapp.net:27020/?replicaSet=mongors" which is untrue - you would need to set all three nodes up in the same instance for this to be the case.

      Attachments

        Activity

          People

            andre.defrere@mongodb.com Andre de Frere
            andre.defrere@mongodb.com Andre de Frere
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              11 years, 8 weeks, 6 days ago