On 2/9/2015 8:49 PM, Avanish Raju wrote: > I'm using self-signed certificates between my SolrCloud (4.10.3 > <http://mirror.sdunix.com/apache/lucene/solr/ref-guide/apache-solr-ref-guide-4.10.pdf>) > instance and Curl/Solr http client with needClientAuth=true on jetty.xml. > I'm able to load the Solr home page, and also make select/query calls and > they work fine. > > However, when I make any Collections API calls, Basically any of the calls > that are based on "https://localhost:8984/solr/admin/collections?action="; > even using Curl locally, and a .pem file, some of the requests work, and > some of them(about 1 in 3 or more) hang indefinitely. > > Has anyone run into this? How can I fix this?
SolrCloud, especially with things like the collections API, does a lot of communication between nodes. If the nodes are configured to require authentication, you must configure Solr itself to provide that authentication when it is acting as a client. SOLR-4407 discusses this for situations where the authentication uses certificates, which apparently works now if you provide the cert to each Solr instance in the form of a java keystore. https://issues.apache.org/jira/browse/SOLR-4407 Thanks, Shawn
