Very well explained. Thanks. Yes, we do optimize Index before replication. I am not particularly worried about disk space usage. I was more curious of that behavior.
*Pranav Prakash* "temet nosce" Twitter <http://twitter.com/pranavprakash> | Blog <http://blog.myblive.com> | Google <http://www.google.com/profiles/pranny> On Wed, Aug 10, 2011 at 19:55, Erick Erickson <erickerick...@gmail.com>wrote: > This is expected behavior. You might be optimizing > your index on the master after every set of changes, > in which case the entire index is copied. During this > period, the space on disk will at least double, there's no > way around that. > > If you do NOT optimize, then the slave will only copy changed > segments instead of the entire index. Optimizing isn't > usually necessary except periodically (daily, perhaps weekly, > perhaps never actually). > > All that said, depending on how merging happens, you will always > have the possibility of the entire index being copied sometimes > because you'll happen to hit a merge that merges all segments > into one. > > There are some advanced options that can control some parts > of merging, but you need to get to the bottom of why the whole > index is getting copied every time before you go there. I'd bet > you're issuing an optimize. > > Best > Erick > > On Wed, Aug 10, 2011 at 5:30 AM, Pranav Prakash <pra...@gmail.com> wrote: > > That is not true. Replication is roughly a copy of the diff between the > >>> master and the slave's index. > >> > >> > > In my case, during replication entire index is copied from master to > slave, > > during which the size of index goes a little over double. Then it shrinks > to > > its original size. Am I doing something wrong? How can I get the master > to > > serve only delta index instead of serving whole index and the slaves > merging > > the new and old index? > > > > *Pranav Prakash* > > >
