[DOCS-890] Tutorial for setting up a replica set on Azure has many errors Created: 14/Dec/12  Updated: 18/Jan/13  Resolved: 18/Jan/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andre de Frere Assignee: Andre de Frere
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 11 years, 8 weeks, 6 days ago

 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.


 Comments   
Comment by Andre de Frere [ 20/Dec/12 ]

sridhar Yeah, I realised half way through changing this that we had intended them to connect to an existing virtual machine. In the original docs, we had them create a new virtual machine (even though the screenshot showed the dialog for connecting to an existing virtual machine). After that I edited everything so it was connecting to an existing virtual machine, and it made sense why we were changing default ports etc.

Comment by Sridhar Nanjundeswaran [ 20/Dec/12 ]

Review Andre's changes. Looks like there were minor edits. Good catch on the replica set config. I will fix a couple of other issues that are still existing. Comments on the issues raised by Andre
1) Instance 2 should have the same DNS as instance 1. This will be allowed because we choose connect to existing virtual machine. This is what we want
2) We have to change the default SSH ports since you have a single DNS for all 3 instances and we need to be able to indiv connect to each of them
3) The rs connect string is correct. Basically you have 1 public DNS/IP for all 3 instances and we attach to the indiv ones by using diff ports

Comment by Sam Kleinman (Inactive) [ 14/Dec/12 ]

Andre, can you coordinate with sridhar on the review of this?

Comment by Andre de Frere [ 14/Dec/12 ]

I've done all the edits I found, potentially the document needs a review

Comment by Andre de Frere [ 14/Dec/12 ]

Looking at the original DOCS ticket for this tutorial (DOCS-359) it would appear that instead of setting up three standalone instances, it was originally intended to set up one standalone and have the other two connect to them. This makes some sense considering how the page is written, but invalidates half the steps for Instance 2. I'm going to run thru the tutorial again and makes sure this all works given the original intent

Comment by Andre de Frere [ 14/Dec/12 ]

As these are just Wiki changes, I'm editing as I go - unfortunately confluence is unstable this afternoon.

Generated at Thu Feb 08 07:39:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.