You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by "Branham, Jeremy [HR]" <Je...@sprint.com> on 2013/10/22 22:01:55 UTC
SOLR Cloud node link is wrong in the admin panel
I'm thinking I might have a configuration problem...
The SOLR Cloud node link is wrong in the admin panel.
I am running solr on port 8080 in JBOSS, but the SOLR cloud admin panel has links to http://192.168.1.123:8983/solr for example.
Also the context should be svc instead of solr.
Is this a configuration problem, or are there some hardcoded values?
Thanks,
Jeremy D. Branham
Performance Technologist II
Sprint University Performance Support
Fort Worth, TX | Tel: **DOTNET
http://JeremyBranham.Wordpress.com<http://jeremybranham.wordpress.com/>
http://www.linkedin.com/in/jeremybranham
________________________________
This e-mail may contain Sprint proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.
Re: SOLR Cloud node link is wrong in the admin panel
Posted by Shawn Heisey <so...@elyograg.org>.
On 10/23/2013 7:50 AM, Branham, Jeremy [HR] wrote:
> It seems the parameters in solr.xml are being ignored.
>
> <?xml version="1.0" encoding="UTF-8" ?>
> <solr persistent="true" sharedLib="lib" zkHost="192.168.1.102:2181" host="localhost" hostPort="8080" hostContext="/svc/solr">
> <cores adminPath="/admin/cores">
> <core schema="schema.xml" instanceDir="root/" name="test" shard="shard1" collection="test" dataDir="/data/v8p/solr/test/data"/>
> </cores>
> </solr>
Did you restart Solr (actually your container - jetty, tomcat, etc)
after making that change? You'll need to make the change on all your
Solr instances and restart them all.
Thanks,
Shawn
RE: SOLR Cloud node link is wrong in the admin panel
Posted by "Branham, Jeremy [HR]" <Je...@sprint.com>.
It seems the parameters in solr.xml are being ignored.
<?xml version="1.0" encoding="UTF-8" ?>
<solr persistent="true" sharedLib="lib" zkHost="192.168.1.102:2181" host="localhost" hostPort="8080" hostContext="/svc/solr">
<cores adminPath="/admin/cores">
<core schema="schema.xml" instanceDir="root/" name="test" shard="shard1" collection="test" dataDir="/data/v8p/solr/test/data"/>
</cores>
</solr>
Jeremy D. Branham
Performance Technologist II
Sprint University Performance Support
Fort Worth, TX | Tel: **DOTNET
http://JeremyBranham.Wordpress.com
http://www.linkedin.com/in/jeremybranham
-----Original Message-----
From: Shawn Heisey [mailto:solr@elyograg.org]
Sent: Tuesday, October 22, 2013 3:14 PM
To: solr-user@lucene.apache.org
Subject: Re: SOLR Cloud node link is wrong in the admin panel
On 10/22/2013 2:01 PM, Branham, Jeremy [HR] wrote:
> I'm thinking I might have a configuration problem...
>
> The SOLR Cloud node link is wrong in the admin panel.
>
> I am running solr on port 8080 in JBOSS, but the SOLR cloud admin panel has links to http://192.168.1.123:8983/solr for example.
> Also the context should be svc instead of solr.
>
> Is this a configuration problem, or are there some hardcoded values?
You're going to need to define the hostPort value in your solr.xml file. In the example solr.xml, this is set to the following string:
${jetty.port:8983}
This means that it will use the java property "jetty.port" unless that's not defined, in which case it will use 8983. Just remove this from hostPort and put 8080 in there.
http://wiki.apache.org/solr/SolrCloud#SolrCloud_Instance_Params
You might ask why Solr doesn't just figure out what port it is running on and store what it finds in the cloudstate. The reason it doesn't do that is because it can't - a java webapp/servlet has no idea what port it's on until it actually receives a request, but it's not going to receive any requests until it's initialized, and by then it's too late to do anything useful with the information ... plus you need to send it a request. This is one of the prime motivating factors behind the project's decision that Solr will no longer be a war in a future major version.
Thanks,
Shawn
________________________________
This e-mail may contain Sprint proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.
Re: SOLR Cloud node link is wrong in the admin panel
Posted by Shawn Heisey <so...@elyograg.org>.
On 10/22/2013 2:01 PM, Branham, Jeremy [HR] wrote:
> I'm thinking I might have a configuration problem...
>
> The SOLR Cloud node link is wrong in the admin panel.
>
> I am running solr on port 8080 in JBOSS, but the SOLR cloud admin panel has links to http://192.168.1.123:8983/solr for example.
> Also the context should be svc instead of solr.
>
> Is this a configuration problem, or are there some hardcoded values?
You're going to need to define the hostPort value in your solr.xml
file. In the example solr.xml, this is set to the following string:
${jetty.port:8983}
This means that it will use the java property "jetty.port" unless that's
not defined, in which case it will use 8983. Just remove this from
hostPort and put 8080 in there.
http://wiki.apache.org/solr/SolrCloud#SolrCloud_Instance_Params
You might ask why Solr doesn't just figure out what port it is running
on and store what it finds in the cloudstate. The reason it doesn't do
that is because it can't - a java webapp/servlet has no idea what port
it's on until it actually receives a request, but it's not going to
receive any requests until it's initialized, and by then it's too late
to do anything useful with the information ... plus you need to send it
a request. This is one of the prime motivating factors behind the
project's decision that Solr will no longer be a war in a future major
version.
Thanks,
Shawn