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 okayndc <bo...@gmail.com> on 2011/09/07 16:01:41 UTC

running SOLR on same server as your website

Hi everyone!

Is it not a good practice to run SOLR on the same server where you website
files sit?  Or is it a MUST to house SOLR on it's own application server?
The problem that I'm facing is that, my website's files sit on a servlet
container (Tomcat) and I think it would be more convenient to house the SOLR
instance on the same server?  Is this not a good idea?  What is your SOLR
setup?

Thanks

Re: running SOLR on same server as your website

Posted by okayndc <bo...@gmail.com>.
In the context of "application", I assume that you mean SOLRJ (for example)?

On Wed, Sep 7, 2011 at 10:04 AM, Erik Hatcher <er...@gmail.com>wrote:

> It's not necessarily a bad idea... as long as you secure it properly such
> that user requests cannot hit Solr, only requests from your application can
> do so.
>
> Eventually, perhaps, scale would be an issue and you'd want/need to
> separate the tiers, but as long as you've got security and scalability
> covered there's no reason not to deploy together like that.
>
>        Erik
>
> On Sep 7, 2011, at 10:01 , okayndc wrote:
>
> > Hi everyone!
> >
> > Is it not a good practice to run SOLR on the same server where you
> website
> > files sit?  Or is it a MUST to house SOLR on it's own application server?
> > The problem that I'm facing is that, my website's files sit on a servlet
> > container (Tomcat) and I think it would be more convenient to house the
> SOLR
> > instance on the same server?  Is this not a good idea?  What is your SOLR
> > setup?
> >
> > Thanks
>
>

Re: running SOLR on same server as your website

Posted by Erik Hatcher <er...@gmail.com>.
It's not necessarily a bad idea... as long as you secure it properly such that user requests cannot hit Solr, only requests from your application can do so.

Eventually, perhaps, scale would be an issue and you'd want/need to separate the tiers, but as long as you've got security and scalability covered there's no reason not to deploy together like that.

	Erik

On Sep 7, 2011, at 10:01 , okayndc wrote:

> Hi everyone!
> 
> Is it not a good practice to run SOLR on the same server where you website
> files sit?  Or is it a MUST to house SOLR on it's own application server?
> The problem that I'm facing is that, my website's files sit on a servlet
> container (Tomcat) and I think it would be more convenient to house the SOLR
> instance on the same server?  Is this not a good idea?  What is your SOLR
> setup?
> 
> Thanks


RE: running SOLR on same server as your website

Posted by Tim Gilbert <TI...@morningstar.com>.
Just make sure that outside users can't talk directly to your solr
instance.  If they can talk to Solr, they can add/delete documents which
will affect your site.

Tim

-----Original Message-----
From: okayndc [mailto:bodymoves@gmail.com] 
Sent: Wednesday, September 07, 2011 10:45 AM
To: solr-user@lucene.apache.org
Subject: Re: running SOLR on same server as your website

Right now, the index is relatively small in size ~less than 1mb.  I
think
right now, it's okay but, a couple years down the road, we may have to
transfer SOLR onto a separate application server.

On Wed, Sep 7, 2011 at 10:15 AM, Jaeger, Jay - DOT
<Ja...@dot.wi.gov>wrote:

> You could host Solr inside the same Tomcat container, or in a
different
> servlet container (say, a second Tomcat instance) on the same server.
>
> Be aware of your OS memory requirements, though:  In my experience,
Solr
> performs best when it has lots of OS memory to cache index files (at
least,
> if your index is very big).  For that reason alone, we chose to host
our
> Solr instance (used internally only) in a separate virtual machine in
its
> own web app server instance.
>
> It is all a matter of managing your memory, CPU and disk performance.
If
> those are already constrained or nearly constrained on your website,
then
> adding Solr into that mix is probably not such a good idea.  If those
are
> not issues on your existing website, and your Solr load is modest,
then you
> can probably squeeze it onto the same server.
>
> Like most real-world answers, it comes down to "it depends".
>
> JRJ
>
> -----Original Message-----
> From: okayndc [mailto:bodymoves@gmail.com]
> Sent: Wednesday, September 07, 2011 9:02 AM
> To: solr-user@lucene.apache.org
> Subject: running SOLR on same server as your website
>
> Hi everyone!
>
> Is it not a good practice to run SOLR on the same server where you
website
> files sit?  Or is it a MUST to house SOLR on it's own application
server?
> The problem that I'm facing is that, my website's files sit on a
servlet
> container (Tomcat) and I think it would be more convenient to house
the
> SOLR
> instance on the same server?  Is this not a good idea?  What is your
SOLR
> setup?
>
> Thanks
>

Re: running SOLR on same server as your website

Posted by okayndc <bo...@gmail.com>.
Right now, the index is relatively small in size ~less than 1mb.  I think
right now, it's okay but, a couple years down the road, we may have to
transfer SOLR onto a separate application server.

On Wed, Sep 7, 2011 at 10:15 AM, Jaeger, Jay - DOT <Ja...@dot.wi.gov>wrote:

> You could host Solr inside the same Tomcat container, or in a different
> servlet container (say, a second Tomcat instance) on the same server.
>
> Be aware of your OS memory requirements, though:  In my experience, Solr
> performs best when it has lots of OS memory to cache index files (at least,
> if your index is very big).  For that reason alone, we chose to host our
> Solr instance (used internally only) in a separate virtual machine in its
> own web app server instance.
>
> It is all a matter of managing your memory, CPU and disk performance.  If
> those are already constrained or nearly constrained on your website, then
> adding Solr into that mix is probably not such a good idea.  If those are
> not issues on your existing website, and your Solr load is modest, then you
> can probably squeeze it onto the same server.
>
> Like most real-world answers, it comes down to "it depends".
>
> JRJ
>
> -----Original Message-----
> From: okayndc [mailto:bodymoves@gmail.com]
> Sent: Wednesday, September 07, 2011 9:02 AM
> To: solr-user@lucene.apache.org
> Subject: running SOLR on same server as your website
>
> Hi everyone!
>
> Is it not a good practice to run SOLR on the same server where you website
> files sit?  Or is it a MUST to house SOLR on it's own application server?
> The problem that I'm facing is that, my website's files sit on a servlet
> container (Tomcat) and I think it would be more convenient to house the
> SOLR
> instance on the same server?  Is this not a good idea?  What is your SOLR
> setup?
>
> Thanks
>

RE: running SOLR on same server as your website

Posted by "Jaeger, Jay - DOT" <Ja...@dot.wi.gov>.
You could host Solr inside the same Tomcat container, or in a different servlet container (say, a second Tomcat instance) on the same server.

Be aware of your OS memory requirements, though:  In my experience, Solr performs best when it has lots of OS memory to cache index files (at least, if your index is very big).  For that reason alone, we chose to host our Solr instance (used internally only) in a separate virtual machine in its own web app server instance.

It is all a matter of managing your memory, CPU and disk performance.  If those are already constrained or nearly constrained on your website, then adding Solr into that mix is probably not such a good idea.  If those are not issues on your existing website, and your Solr load is modest, then you can probably squeeze it onto the same server.

Like most real-world answers, it comes down to "it depends".

JRJ

-----Original Message-----
From: okayndc [mailto:bodymoves@gmail.com] 
Sent: Wednesday, September 07, 2011 9:02 AM
To: solr-user@lucene.apache.org
Subject: running SOLR on same server as your website

Hi everyone!

Is it not a good practice to run SOLR on the same server where you website
files sit?  Or is it a MUST to house SOLR on it's own application server?
The problem that I'm facing is that, my website's files sit on a servlet
container (Tomcat) and I think it would be more convenient to house the SOLR
instance on the same server?  Is this not a good idea?  What is your SOLR
setup?

Thanks