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 Bill Au <bi...@gmail.com> on 2012/12/05 16:30:31 UTC

setting hostPort for SolrCloud

Can hostPort for SolrCloud only be set in solr.xml?  I tried setting the
system property hostPort and jetty.port on the Java command line but
neither of them work.

Bill

Re: setting hostPort for SolrCloud

Posted by Mark Miller <ma...@gmail.com>.
It is set in solr.xml, but solr.xml has a syntax that allows you to set values by system properties.

By default solr.xml is setup so that the jetty.port system property should set the hostPort. I'm sure that works in general, so I'm not sure why it's not working for you.

Can you provide your solr.xml?

- Mark

On Dec 5, 2012, at 7:30 AM, Bill Au <bi...@gmail.com> wrote:

> Can hostPort for SolrCloud only be set in solr.xml?  I tried setting the
> system property hostPort and jetty.port on the Java command line but
> neither of them work.
> 
> Bill


Re: setting hostPort for SolrCloud

Posted by Bill Au <bi...@gmail.com>.
Thanks for the information.

Bill


On Fri, Dec 7, 2012 at 3:04 PM, Mark Miller <ma...@gmail.com> wrote:

> Yup, solr.xml is pretty much required - especially if you want to use
> solrcloud.
>
> The only reason anything works without is for back compat.
>
> We are working towards removing the need for it, but's considered required
> these days.
>
> - Mark
>
> On Dec 7, 2012, at 11:04 AM, Bill Au <bi...@gmail.com> wrote:
>
> > I actually was not using a solr.xml.  I am only using a single core.  I
> am
> > using the default core name collection1.  I know for sure I will not be
> > using more than a single core so I did not bother with having a solr.xml.
> > Is that a bad thing?
> >
> > Everything works when I had tomcat config to run on port 8983.  But once
> I
> > configure tomcat to use a different port, I notice that SolrCloud is
> still
> > using port 8983 so it wasn't working.  I then tried adding
> > "-Djetty.port=8000" and "-DhostPort=8000" to the environment variable
> > JAVA_OPTS before running the tomcat start script bin/startup.sh.  But
> > SolrCloud was still using 8983.  I ended up setting hostPort in solr.xml
> > and got things working.
> >
> > It solr.xml is required, then I can just set the port for SolrCloud in
> > there.  But I was hoping I did not have to bother with solr.xml at all.
> > One less configuration file, one less thing that can go wrong.
> >
> > Bill
> >
> >
> > On Wed, Dec 5, 2012 at 4:40 PM, Mark Miller <ma...@gmail.com>
> wrote:
> >
> >> Be aware that you still have to setup tomcat to run Solr on the right
> port
> >> - and you also have to provide the port to Solr on startup. With jetty
> we
> >> do both with -Djetty.port - with Tomcat you have to setup Tomcat to run
> on
> >> the right port *and* tell Solr what that port is. By default that means
> >> also passing -Djetty.port - but you can change that to whatever you
> want in
> >> solr.xml (to hostPort or solr.port or whatever).
> >>
> >> The problem is that it's difficult for a webapp to find what ports it's
> >> running on - you can only do it when a request actually comes in to my
> >> knowledge.
> >>
> >> - Mark
> >>
> >> On Dec 5, 2012, at 1:05 PM, Bill Au <bi...@gmail.com> wrote:
> >>
> >>> I am using tomcat.  In my tomcat start script I have tried setting
> system
> >>> properties with both
> >>>
> >>> -Djetty.port=8080
> >>>
> >>> and
> >>>
> >>> -DhostPort=8080
> >>>
> >>> but neither changed the host port for SolrCloud.  It still uses the
> >> default
> >>> 8983.
> >>>
> >>> Bill
> >>>
> >>>
> >>> On Wed, Dec 5, 2012 at 12:11 PM, Jack Krupansky <
> jack@basetechnology.com
> >>> wrote:
> >>>
> >>>> Solr runs in a container and the container controls the port. So, you
> >> need
> >>>> to tell the container which port to use.
> >>>>
> >>>> For example,
> >>>>
> >>>> java -Djetty.port=8180 -jar start.jar
> >>>>
> >>>> -- Jack Krupansky
> >>>>
> >>>> -----Original Message----- From: Bill Au
> >>>> Sent: Wednesday, December 05, 2012 10:30 AM
> >>>> To: solr-user@lucene.apache.org
> >>>> Subject: setting hostPort for SolrCloud
> >>>>
> >>>>
> >>>> Can hostPort for SolrCloud only be set in solr.xml?  I tried setting
> the
> >>>> system property hostPort and jetty.port on the Java command line but
> >>>> neither of them work.
> >>>>
> >>>> Bill
> >>>>
> >>
> >>
>
>

Re: setting hostPort for SolrCloud

Posted by Mark Miller <ma...@gmail.com>.
Yup, solr.xml is pretty much required - especially if you want to use solrcloud.

The only reason anything works without is for back compat.

We are working towards removing the need for it, but's considered required these days.

- Mark

On Dec 7, 2012, at 11:04 AM, Bill Au <bi...@gmail.com> wrote:

> I actually was not using a solr.xml.  I am only using a single core.  I am
> using the default core name collection1.  I know for sure I will not be
> using more than a single core so I did not bother with having a solr.xml.
> Is that a bad thing?
> 
> Everything works when I had tomcat config to run on port 8983.  But once I
> configure tomcat to use a different port, I notice that SolrCloud is still
> using port 8983 so it wasn't working.  I then tried adding
> "-Djetty.port=8000" and "-DhostPort=8000" to the environment variable
> JAVA_OPTS before running the tomcat start script bin/startup.sh.  But
> SolrCloud was still using 8983.  I ended up setting hostPort in solr.xml
> and got things working.
> 
> It solr.xml is required, then I can just set the port for SolrCloud in
> there.  But I was hoping I did not have to bother with solr.xml at all.
> One less configuration file, one less thing that can go wrong.
> 
> Bill
> 
> 
> On Wed, Dec 5, 2012 at 4:40 PM, Mark Miller <ma...@gmail.com> wrote:
> 
>> Be aware that you still have to setup tomcat to run Solr on the right port
>> - and you also have to provide the port to Solr on startup. With jetty we
>> do both with -Djetty.port - with Tomcat you have to setup Tomcat to run on
>> the right port *and* tell Solr what that port is. By default that means
>> also passing -Djetty.port - but you can change that to whatever you want in
>> solr.xml (to hostPort or solr.port or whatever).
>> 
>> The problem is that it's difficult for a webapp to find what ports it's
>> running on - you can only do it when a request actually comes in to my
>> knowledge.
>> 
>> - Mark
>> 
>> On Dec 5, 2012, at 1:05 PM, Bill Au <bi...@gmail.com> wrote:
>> 
>>> I am using tomcat.  In my tomcat start script I have tried setting system
>>> properties with both
>>> 
>>> -Djetty.port=8080
>>> 
>>> and
>>> 
>>> -DhostPort=8080
>>> 
>>> but neither changed the host port for SolrCloud.  It still uses the
>> default
>>> 8983.
>>> 
>>> Bill
>>> 
>>> 
>>> On Wed, Dec 5, 2012 at 12:11 PM, Jack Krupansky <jack@basetechnology.com
>>> wrote:
>>> 
>>>> Solr runs in a container and the container controls the port. So, you
>> need
>>>> to tell the container which port to use.
>>>> 
>>>> For example,
>>>> 
>>>> java -Djetty.port=8180 -jar start.jar
>>>> 
>>>> -- Jack Krupansky
>>>> 
>>>> -----Original Message----- From: Bill Au
>>>> Sent: Wednesday, December 05, 2012 10:30 AM
>>>> To: solr-user@lucene.apache.org
>>>> Subject: setting hostPort for SolrCloud
>>>> 
>>>> 
>>>> Can hostPort for SolrCloud only be set in solr.xml?  I tried setting the
>>>> system property hostPort and jetty.port on the Java command line but
>>>> neither of them work.
>>>> 
>>>> Bill
>>>> 
>> 
>> 


Re: setting hostPort for SolrCloud

Posted by Bill Au <bi...@gmail.com>.
 I actually was not using a solr.xml.  I am only using a single core.  I am
using the default core name collection1.  I know for sure I will not be
using more than a single core so I did not bother with having a solr.xml.
Is that a bad thing?

Everything works when I had tomcat config to run on port 8983.  But once I
configure tomcat to use a different port, I notice that SolrCloud is still
using port 8983 so it wasn't working.  I then tried adding
"-Djetty.port=8000" and "-DhostPort=8000" to the environment variable
JAVA_OPTS before running the tomcat start script bin/startup.sh.  But
SolrCloud was still using 8983.  I ended up setting hostPort in solr.xml
and got things working.

It solr.xml is required, then I can just set the port for SolrCloud in
there.  But I was hoping I did not have to bother with solr.xml at all.
One less configuration file, one less thing that can go wrong.

Bill


On Wed, Dec 5, 2012 at 4:40 PM, Mark Miller <ma...@gmail.com> wrote:

> Be aware that you still have to setup tomcat to run Solr on the right port
> - and you also have to provide the port to Solr on startup. With jetty we
> do both with -Djetty.port - with Tomcat you have to setup Tomcat to run on
> the right port *and* tell Solr what that port is. By default that means
> also passing -Djetty.port - but you can change that to whatever you want in
> solr.xml (to hostPort or solr.port or whatever).
>
> The problem is that it's difficult for a webapp to find what ports it's
> running on - you can only do it when a request actually comes in to my
> knowledge.
>
> - Mark
>
> On Dec 5, 2012, at 1:05 PM, Bill Au <bi...@gmail.com> wrote:
>
> > I am using tomcat.  In my tomcat start script I have tried setting system
> > properties with both
> >
> > -Djetty.port=8080
> >
> > and
> >
> > -DhostPort=8080
> >
> > but neither changed the host port for SolrCloud.  It still uses the
> default
> > 8983.
> >
> > Bill
> >
> >
> > On Wed, Dec 5, 2012 at 12:11 PM, Jack Krupansky <jack@basetechnology.com
> >wrote:
> >
> >> Solr runs in a container and the container controls the port. So, you
> need
> >> to tell the container which port to use.
> >>
> >> For example,
> >>
> >> java -Djetty.port=8180 -jar start.jar
> >>
> >> -- Jack Krupansky
> >>
> >> -----Original Message----- From: Bill Au
> >> Sent: Wednesday, December 05, 2012 10:30 AM
> >> To: solr-user@lucene.apache.org
> >> Subject: setting hostPort for SolrCloud
> >>
> >>
> >> Can hostPort for SolrCloud only be set in solr.xml?  I tried setting the
> >> system property hostPort and jetty.port on the Java command line but
> >> neither of them work.
> >>
> >> Bill
> >>
>
>

Re: setting hostPort for SolrCloud

Posted by Mark Miller <ma...@gmail.com>.
Be aware that you still have to setup tomcat to run Solr on the right port - and you also have to provide the port to Solr on startup. With jetty we do both with -Djetty.port - with Tomcat you have to setup Tomcat to run on the right port *and* tell Solr what that port is. By default that means also passing -Djetty.port - but you can change that to whatever you want in solr.xml (to hostPort or solr.port or whatever).

The problem is that it's difficult for a webapp to find what ports it's running on - you can only do it when a request actually comes in to my knowledge.

- Mark

On Dec 5, 2012, at 1:05 PM, Bill Au <bi...@gmail.com> wrote:

> I am using tomcat.  In my tomcat start script I have tried setting system
> properties with both
> 
> -Djetty.port=8080
> 
> and
> 
> -DhostPort=8080
> 
> but neither changed the host port for SolrCloud.  It still uses the default
> 8983.
> 
> Bill
> 
> 
> On Wed, Dec 5, 2012 at 12:11 PM, Jack Krupansky <ja...@basetechnology.com>wrote:
> 
>> Solr runs in a container and the container controls the port. So, you need
>> to tell the container which port to use.
>> 
>> For example,
>> 
>> java -Djetty.port=8180 -jar start.jar
>> 
>> -- Jack Krupansky
>> 
>> -----Original Message----- From: Bill Au
>> Sent: Wednesday, December 05, 2012 10:30 AM
>> To: solr-user@lucene.apache.org
>> Subject: setting hostPort for SolrCloud
>> 
>> 
>> Can hostPort for SolrCloud only be set in solr.xml?  I tried setting the
>> system property hostPort and jetty.port on the Java command line but
>> neither of them work.
>> 
>> Bill
>> 


Re: setting hostPort for SolrCloud

Posted by Bill Au <bi...@gmail.com>.
I am using tomcat.  In my tomcat start script I have tried setting system
properties with both

-Djetty.port=8080

and

-DhostPort=8080

but neither changed the host port for SolrCloud.  It still uses the default
8983.

Bill


On Wed, Dec 5, 2012 at 12:11 PM, Jack Krupansky <ja...@basetechnology.com>wrote:

> Solr runs in a container and the container controls the port. So, you need
> to tell the container which port to use.
>
> For example,
>
> java -Djetty.port=8180 -jar start.jar
>
> -- Jack Krupansky
>
> -----Original Message----- From: Bill Au
> Sent: Wednesday, December 05, 2012 10:30 AM
> To: solr-user@lucene.apache.org
> Subject: setting hostPort for SolrCloud
>
>
> Can hostPort for SolrCloud only be set in solr.xml?  I tried setting the
> system property hostPort and jetty.port on the Java command line but
> neither of them work.
>
> Bill
>

Re: setting hostPort for SolrCloud

Posted by Jack Krupansky <ja...@basetechnology.com>.
Solr runs in a container and the container controls the port. So, you need 
to tell the container which port to use.

For example,

java -Djetty.port=8180 -jar start.jar

-- Jack Krupansky

-----Original Message----- 
From: Bill Au
Sent: Wednesday, December 05, 2012 10:30 AM
To: solr-user@lucene.apache.org
Subject: setting hostPort for SolrCloud

Can hostPort for SolrCloud only be set in solr.xml?  I tried setting the
system property hostPort and jetty.port on the Java command line but
neither of them work.

Bill