On 10/1/2015 4:43 AM, Adrian Liew wrote: > E:\solr-5.3.0\bin>solr.cmd create_collection -c sitecore_core_index -n > sitecore_ > common_configs -shards 1 -replicationFactor 3 > > Connecting to ZooKeeper at 10.0.0.4:2181,10.0.0.5:2182,10.0.0.6:2183 ... > Re-using existing configuration directory sitecore_common_configs > > Creating new collection 'sitecore_core_index' using command: > http://localhost:8983/solr/admin/collections?action=CREATE&name=sitecore_core_in > dex&numShards=1&replicationFactor=3&maxShardsPerNode=2&collection.configName=sit > ecore_common_configs > > ERROR: Failed to create collection 'sitecore_core_index' due to: create the > coll > ection time out:180s
The timeout, as it mentions, is 180 seconds, or three minutes. This is a the default timeout for the Collections API, and it is a particularly long timeout. When it is exceeded, it is usually an indication of a serious problem. The collection create will likely succeed eventually, after an unknown amount of time ... the collections API just gave up on waiting for the response. There are two things that I know of that can cause this: A very large number of collections, and general performance issues. I did some testing a while back with thousands of empty collections on the Solr 5.x cloud example. It did not turn out well. Many things timed out, and a server restart would throw the whole cloud into chaos for a very long time. If those collections were not empty, then I suspect the problems would be even worse. General performance issues (usually RAM-related) can cause big problems with SolrCloud too. The following wiki page is most of my accumulated knowledge about what causes performance problems with Solr: https://wiki.apache.org/solr/SolrPerformanceProblems Thanks, Shawn
