I’d like to ensure an extended warmup is done on each SolrCloud node prior to that node serving traffic. I can do certain things prior to starting Solr, such as pump the index dir through /dev/null to pre-warm the filesystem cache, and post-start I can use the ping handler with a health check file to prevent the node from entering the clients load balancer until I’m ready. What I seem to be missing is control over when a node starts participating in queries sent to the other nodes.
I can, of course, add solrconfig.xml firstSearcher queries, which I assume (and fervently hope!) happens before a node registers itself in ZK clusterstate.json as ready for work, but that doesn’t scale so well if I want that initial warmup to run thousands of queries, or run them with some paralleism. I’m storing solrconfig.xml in ZK, so I’m sensitive to the size. Any ideas, or corrections to my assumptions? Thanks.
