this message in context:
http://lucene.472066.n3.nabble.com/Is-optimize-needed-on-slaves-if-it-replicates-from-optimized-master-tp3241604p3987086.html
Sent from the Solr - User mailing list archive at Nabble.com.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Is-optimize-needed-on-slaves-if-it-replicates-from-optimized-master-tp3241604p3987086.html
Sent from the Solr - User mailing list archive at Nabble.com.
in context:
http://lucene.472066.n3.nabble.com/Is-optimize-needed-on-slaves-if-it-replicates-from-optimized-master-tp3241604p3986597.html
Sent from the Solr - User mailing list archive at Nabble.com.
in sync), only the modified segments would be transferred
just like the non-optimized index transfer. Am I right?
Regards,
Sudarshan
--
View this message in context:
http://lucene.472066.n3.nabble.com/Is-optimize-needed-on-slaves-if-it-replicates-from-optimized-master
) between the master and the
slave to initiate replication?
Your suggestions/guidance would me very helpful to get a clear
understanding. Please help.
Thanks,
Sudarshan
--
View this message in context:
http://lucene.472066.n3.nabble.com/Is-optimize-needed-on-slaves-if-it-replicates-from-optimized
) between the master and the
slave to initiate replication?
Your suggestions/guidance would me very helpful to get a clear
understanding. Please help.
Thanks,
Sudarshan
--
View this message in context:
http://lucene.472066.n3.nabble.com/Is-optimize-needed-on-slaves-if-it-replicates-from
From what I see on my slaves, yes.
After replication has finished and new index is in place and new reader has
started
I have always a write.lock file in my index directory on slaves, even though
the index
on master is optimized.
Regards
Bernd
Am 10.08.2011 09:12, schrieb Pranav Prakash:
On Wed, Aug 10, 2011 at 1:11 PM, Bernd Fehling
bernd.fehl...@uni-bielefeld.de wrote:
From what I see on my slaves, yes.
After replication has finished and new index is in place and new reader has
started
I have always a write.lock file in my index directory on slaves, even
though the index
Sure there is actually no optimizing on the slave needed,
but after calling optimize on the slave the write.lock will be removed.
So why is the replication process not doing this?
Regards
Bernd
Am 10.08.2011 10:57, schrieb Shalin Shekhar Mangar:
On Wed, Aug 10, 2011 at 1:11 PM, Bernd Fehling
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
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
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
12 matches
Mail list logo
