Wondering if anyone has experience with replicating large indexes. We have a
Solr deployment with 1 master, 1 master/slave and 5 slaves. Our index contains
15+ million articles and is ~55GB in size.
Performance is great on all systems.
Debian Linux
Apache-Tomcat
100GB disk
6GB RAM
2 proc
on VMWare ESXi 4.0
We notice however that whenever the master is optimized, the complete index is
replicated to the slaves. This causes a 100%+ bloat in disk requirements.
Is this normal? Is there a way around this?
Currently our optimize is configured as such:
curl
'http://localhost:8080/solr/update?optimize=true&maxSegments=1&waitFlush=true&expungeDeletes=true'
Willing to share our experiences with Solr.
Thanks,
Jason
