In solr.XML, hostPort should be set to 80. Zookeeper tracks the port so the
various nodes can find one another as long as you set it correctly in that
file.
On May 31, 2013 8:38 PM, "cleardot" <clear...@aol.com> wrote:
> I know this issue has been answered somewhere.
>
> I've got SolrCloud running under Tomcat 6, the respective settings are
>
> tomcat6.conf
> -----------------------------------------------------------------------
> <Connector port="80" protocol="HTTP/1.1"
> connectionTimeout="20000"
> redirectPort="8443" />
>
>
> I am deliberately running Tomcat on 80 but on SOLR I stuck with 8983
> because
> it appears to be the default for SolrCloud.
>
>
> solr.xml
> -----------------------------------------------------------------------
> <cores defaultCoreName="collection1" adminPath="/admin/cores"
> zkClientTimeout="${zkClientTimeout:15000}" hostPort="8983"
> hostContext="solr">
> <core loadOnStartup="true" instanceDir="mycore/" transient="false"
> name="mycore"/>
> </cores>
>
>
> In non-solrcloud mode this works fine for updates and queries.
>
> In solrcloud mode (Tomcat startup with the added JAVA_OPTS on both hosts)
> catalina.out shows shard1 and the embedded zookeeper booting nicely and I
> can see the shard2 machine registering with zookeeper.
>
> But any query to the shard1 machine get the dreaded
>
> Connection to http://10.xx.xx.185:8983 refused
>
> I use the same security group for both hosts, with these settings:
>
> TCP Port Service
> 0 - 65535 0.0.0.0/0
> 22 (SSH) 0.0.0.0/0
> 80 (HTTP) 0.0.0.0/0
> 8983 0.0.0.0/0
>
> I cannot tell whether this is a security group problem or some mismatch
> between my SOLR and Tomcat port settings. Any help is appreciated.
>
> Dan
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/solcloud-on-tomcat-the-8983-port-problem-tp4067512.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
