You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Jan Høydahl <ja...@cominvent.com> on 2015/02/04 11:48:02 UTC
Give Solr its "own" port number
Hi,
Until 5.x Solr would start on whatever port of the appserver chosen, i.e. 8983 for Jetty, 8080 for Tomcat etc.
Now that Solr is a "standalone" app, why should we "inherit" Jetty's default port 8983 anymore?
So I propose we pick a brand new port number for Solr to use as default. Benefits:
* Identity - people will immediately identify Solr by its port number. Even IANA?
* Less risk of clash with existing Jetty service on the same server
* We could pick a cleaner port which is not 6 syllables to pronounce :)
PS: Same goes for the default URL. We could move to toplevel now http://localhost:8983/
I realize both of these will break a lot of docs and tools assuming where stuff is,
but it has always been configurable anyway, so it's not a contract we have promised to stick to.
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Give Solr its "own" port number
Posted by Shawn Heisey <ap...@elyograg.org>.
On 2/4/2015 3:48 AM, Jan Høydahl wrote:
> Until 5.x Solr would start on whatever port of the appserver chosen, i.e. 8983 for Jetty, 8080 for Tomcat etc.
> Now that Solr is a "standalone" app, why should we "inherit" Jetty's default port 8983 anymore?
>
> So I propose we pick a brand new port number for Solr to use as default. Benefits:
> * Identity - people will immediately identify Solr by its port number. Even IANA?
> * Less risk of clash with existing Jetty service on the same server
> * We could pick a cleaner port which is not 6 syllables to pronounce :)
>
> PS: Same goes for the default URL. We could move to toplevel now http://localhost:8983/
>
> I realize both of these will break a lot of docs and tools assuming where stuff is,
> but it has always been configurable anyway, so it's not a contract we have promised to stick to.
Pedantic point -- Solr is not yet a standalone app. It's still using
jetty, and most likely a war. Even when it DOES become a standalone app
(which I hope can be soon), I see no reason to change the default port
number. For the end user, it must always be easy to change the port
number if they wish.
If we can get an official port number assignment from IANA, and it's not
8983, then that would be a good reason to change the default port. I
don't know what would be involved in getting an official assignment. It
would be good to avoid the problems encountered when the initial port
for RADIUS was found to already be assigned. Currently 8983 is not
officially assigned, so hopefully we wouldn't run into that pain.
I also don't see any strong reason to eliminate /solr as a default URL
path. It might be easy to do, and even somewhat logical given that a
standalone app won't be serving any additional paths, but it will
require changes to almost all existing user code and large amounts of
official and unofficial documentation, with no definable advantage that
I can see. It might also result in less capability (or a more
complicated configuration) for proxy servers talking to Solr. If a
strong technical argument is put forth for moving to the / path, I'm
willing to reconsider my opinion.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Give Solr its "own" port number
Posted by Jan Høydahl <ja...@cominvent.com>.
> IIRC: 8983 was explicitly picked for Solr years ago because there weren't
> really any other systems out there using it (unlike 8000, 8080, 8888,
> etc...)
Ah, I stand corrected. All these years I've assumed 9983 was a Jetty default.
Well, already having our own port then, it makes no sense to change it.
Saving root url for some set of V2 APIs is also a good idea.
So I rest my case :)
Thanks for your feedback. Should we perhaps pursue IANA registration then?
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Give Solr its "own" port number
Posted by "david.w.smiley@gmail.com" <da...@gmail.com>.
-0 Hoss’s points are my view as well. 8983 is already pretty well known
amongst Solr users.
~ David Smiley
Freelance Apache Lucene/Solr Search Consultant/Developer
http://www.linkedin.com/in/davidwsmiley
On Wed, Feb 4, 2015 at 12:37 PM, Chris Hostetter <ho...@fucit.org>
wrote:
> : Until 5.x Solr would start on whatever port of the appserver chosen,
> i.e. 8983 for Jetty, 8080 for Tomcat etc.
> : Now that Solr is a "standalone" app, why should we "inherit" Jetty's
> default port 8983 anymore?
>
> last time i checked, 8983 is not "Jetty's default port" ... Jetty's
> hardcoded default port is "0" (ie: listen on any port assigned by the OS)
> and jetty's "sample" default (from the jetty.xml they ship to use as a
> default) use port "8080"
>
> IIRC: 8983 was explicitly picked for Solr years ago because there weren't
> really any other systems out there using it (unlike 8000, 8080, 8888,
> etc...)
>
> : * Identity - people will immediately identify Solr by its port number.
> Even IANA?
>
> this is pretty much already true -- and if folks really care about getting
> IANA recognition, then 8983 seems like the best choice since:
> 1) we already have heavy recognition for that port
> 2) it's currently "unassigned" in the IANA port numbers list.
>
> : PS: Same goes for the default URL. We could move to toplevel now
> http://localhost:8983/
>
> -0 ... i don't see any downside to leaving "/solr/" in the URL, and
> if/when we rip out the jetty stack completley and stop beholding to the
> servlet APIs internally it
> gives us flexibility if we want to start deprecating/retring things to be
> able to say "All of the legacy, pre-Solr X.0, APIs use a base path of
> '/solr/' and all the new hotness APIs use a base path of '/v2/'" ... or
> something like that.
>
> ie: worry about it when we have another use for the URL path.
>
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Give Solr its "own" port number
Posted by Chris Hostetter <ho...@fucit.org>.
: Until 5.x Solr would start on whatever port of the appserver chosen, i.e. 8983 for Jetty, 8080 for Tomcat etc.
: Now that Solr is a "standalone" app, why should we "inherit" Jetty's default port 8983 anymore?
last time i checked, 8983 is not "Jetty's default port" ... Jetty's
hardcoded default port is "0" (ie: listen on any port assigned by the OS)
and jetty's "sample" default (from the jetty.xml they ship to use as a
default) use port "8080"
IIRC: 8983 was explicitly picked for Solr years ago because there weren't
really any other systems out there using it (unlike 8000, 8080, 8888,
etc...)
: * Identity - people will immediately identify Solr by its port number. Even IANA?
this is pretty much already true -- and if folks really care about getting
IANA recognition, then 8983 seems like the best choice since:
1) we already have heavy recognition for that port
2) it's currently "unassigned" in the IANA port numbers list.
: PS: Same goes for the default URL. We could move to toplevel now http://localhost:8983/
-0 ... i don't see any downside to leaving "/solr/" in the URL, and
if/when we rip out the jetty stack completley and stop beholding to the
servlet APIs internally it
gives us flexibility if we want to start deprecating/retring things to be
able to say "All of the legacy, pre-Solr X.0, APIs use a base path of
'/solr/' and all the new hotness APIs use a base path of '/v2/'" ... or
something like that.
ie: worry about it when we have another use for the URL path.
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org