Hi folks! I'm studying the migration process from our current solr 3.6 multitenant cluster (single master, multiple slaves) setup to a solrcloud 4.10.3 but I have a a question about the tlog.
First of all, I will try to give some context: - 1 single master and N slaves. - around 300 cores (about 10 per client). Manual sharding, just doc routing per doc language. Example: test-client-en_US, test-client-it_IT, test-client2-en_US. - small indexes. About 2GB per core. Bigger cores contains around 200k docs, others are just heavy denormalized docs (a few thousand, but big documents) - I only do bulk indexing. We have a plenty process that are full reindex, i.e., deleteByQuery=*:* and reindex. - When a full reindex fails, I want to keep the older version. According to the docs, it is recommended to use the autocommit feature and openSearcher=false. But my question is, in my context, can cause any issue not using the autocommit? Outside the extra storage space and the possible delay in the startup time. Another solution I came up with is to create a new collection, issue the full reindex in that collection and "rename" it or create an alias that I can use to query. So, every time I reindex, the "temp" index is created and associated to the alias and the old is deleted. Is this right or a crazy idea? Any thoughts would be appreaciated :) -- Regards, Samuel García.
