That worked. Thanks both of you (Hoss too).
I had in fact set the solr.xml hostPort on both shards to 80 earlier to
match Tomat. But I kept getting
INFO: Update state numShards=null message={
"operation":"state",
"core_node_name":"10.x.x.105:8983_solr_mycore",
"numShards":null,
"shard":"shard2",
"roles":null,
"state":"active",
"core":"mycore",
"collection":"mycore",
"node_name":"10.x.x.105:8983_solr",
"base_url":"http://10.x.x.105:8983/solr"}
when they were initializing (the above being one of many of these INFO
statements). So 8983 was cached somewhere.
If you do not explicitly set hostPort will it default to 8983 or to Tomcat's
port from server.xml?
Dan
--
View this message in context:
http://lucene.472066.n3.nabble.com/solcloud-on-tomcat-the-8983-port-problem-tp4067512p4067522.html
Sent from the Solr - User mailing list archive at Nabble.com.
