Hi , we have a solr cloud instance with 8 nodes and 4 shards. We are starting
to see that index size is growing so huge and when looked at the file system
solr has created several copies of the index.
However using solr admin, I could see its using only on the them.
This is what I see in solr admin.
Index:
/opt/solr/collections/aq-collection/data/index.20140725024044234
Master (Searching)
1406320016969
Gen - 81553
size -58.72 GB.
But when I go in to the file system , This is how it looks.
16G index.20140527220456134
45G index.20140630001131038
4.6G index.20140630090031282
20G index.20140703192128959
1.3G index.20140703200948410
31G index.20140708162308859
52G index.20140716165801658
59G index.20140725024044234
4K index.properties
4K replication.properties
it is actually pointing only to the index.20140725024044234, and using that
for searching and indexing. The timstamps on other indexes are old(about a
month or so)
Can some one explain me why it created so many copies of the index(we did
not create them manually). and how it can be prevented.
Our solr instances are running on solaris VMs
--
View this message in context:
http://lucene.472066.n3.nabble.com/SOLR-cloud-creating-multiple-copies-of-the-same-index-tp4149264.html
Sent from the Solr - User mailing list archive at Nabble.com.
