You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you explain more about secondary collection or share me few pointers?
Will solcolator as a SOLR Update Processor affect or impact the performance of the main purpose of solr collection. e.g indexing the documents and supporting queries?
If we have couple millions of stored queries, can we index them in its own solr cloud and then run document against the cloud? and how to do it?
The text was updated successfully, but these errors were encountered:
it depends on your expectations. If we speak about million queries it can impact the performance of the main collection, so in this case I advise to put Solcolator UP to different collection and set your Indexer to send documents to main Collection and collection with Solcolator.
Yes, if we speak about million queries. Also it's important number CPU you assign to your server. Luwak works good in parallel mode.
Yes, Solcolator collection can be multi-shards. For example, you can do that each shard reads all queries from shared folder (NFS) and then you run documents against this collection.
Read https://github.com/SOLR4189/solcolator#possible-architecture, it mentioned for large number of queries, it suggests a secondary collection which I am not very clear about.
Questions:
The text was updated successfully, but these errors were encountered: