When a core is unloaded it is unregistered from zookeeper and stops taking request, while retaining data on disk(with default params).
Can someone explain what happens internally and how memory, CPU and network bandwidth will be affected if we load/unload shards frequently in SolrCloud setup using core admin API? -Saumitra -- View this message in context: http://lucene.472066.n3.nabble.com/Understanding-core-unload-in-SolrCloud-tp4135714.html Sent from the Solr - User mailing list archive at Nabble.com.
