<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>replication on AdaTheDev Blog</title><link>https://www.adathedev.co.uk/tags/replication/</link><description>Recent content in replication on AdaTheDev Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>adathedev@gmail.com (Adrian Hills)</managingEditor><webMaster>adathedev@gmail.com (Adrian Hills)</webMaster><lastBuildDate>Mon, 21 Feb 2011 11:10:00 +0000</lastBuildDate><atom:link href="https://www.adathedev.co.uk/tags/replication/index.xml" rel="self" type="application/rss+xml"/><item><title>MongoDB replication - oplogSize</title><link>https://www.adathedev.co.uk/2011/02/mongodb-replication-oplogsize.html</link><pubDate>Mon, 21 Feb 2011 11:10:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/02/mongodb-replication-oplogsize.html</guid><description>Background An oplog is a write operation log that MongoDB uses to store data modifications that need to be replicated out to other nodes in the configured set. This oplog is a capped collection which means it will never grow in size beyond a certain point - once it reaches it&amp;rsquo;s max size, old data drops off the end as new data is added so it keeps cycling round. The size of the oplog basically determines how long a secondary node can be down for and still be able to catch up when it comes back online.</description></item></channel></rss>