[DOCS-27] Master-Slave document needs to add a cautionary note about copying slaves and potential errors during startup Created: 08/Jun/10  Updated: 02/Feb/12  Resolved: 02/Feb/12

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

Type: Improvement Priority: Major - P3
Reporter: Chuck Remes Assignee: Sam Kleinman (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

server 1.4.3 64-bit, master-slave configuration


Participants:
Days since reply: 12 years, 2 weeks, 6 days ago

 Description   

Documentation page that needs enhancement is http://www.mongodb.org/display/DOCS/Master+Slave

It specifies that copying a slave to another location and starting it up is sufficient to clone one. However, the startup of the new slave can throw some odd errors like seen here: http://pastie.org/997057

The fix for that specific error is to remove any IP port information from the command line or from an included mongodb configuration file. The source should be specified as a naked IP without port details.



 Comments   
Comment by Chuck Remes [ 02/Feb/12 ]

Sam, I didn't mean any disrespect to you. I was venting a little of my frustration. It wasn't appropriate. I apologize.

I look forward to seeing the improvements to the docs roll out. I'll track them as you suggest.

Comment by Sam Kleinman (Inactive) [ 02/Feb/12 ]

I'm very sorry for delay. I want to thank you for this and other tickets, which do point to very real problems with the documentation that I hope we can deal with promptly. There are a number of tickets that predate my involvement here that I'm trying to go back and resolve in the way that make the most sense in the present, and though it's difficult to delve in the past, I want to make sure that old issues don't rot forever.

I want to reassure you that opening issue on the documentation is very helpful and appreciated. While I understand your hesitancy given the time that it took to get to this one and others, but I would very much look forward to additional documentation issues. We're currently working on the technical review of a major revision of the documentation which we hope to publish in the near future. You can track our progress here:

https://github.com/mongodb/docs

Regards,
sam

Comment by Chuck Remes [ 02/Feb/12 ]

If it takes 18 months for documentation bugs to be processed, why even open any issues?

Comment by Sam Kleinman (Inactive) [ 02/Feb/12 ]

Closing this for the moment, because of the age of the referenced version and the following reason:

It seems that, if this the case and is the case in recent versions, it would make sense to open it as a server issue and we can document the workaround.

Feel free to reopen the ticket.

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