Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of gopalpatwa@gmail.com designates
 209.85.216.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CO1PR04MB44412689765AD48CEFF322F8A240@CO1PR04MB444.namprd04.prod.outlook.com>
References: 
 <CO1PR04MB44463CD13B1E969FD4EE6688A240@CO1PR04MB444.namprd04.prod.outlook.com>
	<54DA3A49.1090604@elyograg.org>
	<CO1PR04MB44412689765AD48CEFF322F8A240@CO1PR04MB444.namprd04.prod.outlook.com>
Date: Tue, 10 Feb 2015 10:37:23 -0800
Message-ID: 
 <CAF62nof+LAFvWZx_BMtaSaReLGL_bNE=1V3meVpPNGXiwqcZHA@mail.gmail.com>
Subject: Re: Solr on Tomcat
From: Gopal Patwa <gopalpatwa@gmail.com>
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=001a11343a4c7ac692050ec02d28

--001a11343a4c7ac692050ec02d28
Content-Type: text/plain; charset=UTF-8

I think until Solr become completely standalone, it could be major task for
all folks who run Solr as war or repackage Solr war maven release to adopt
5.0 release, since they need to remove tomcat or any other  container they
have in production for running Solr.

Not to mention there will tools build for those container to support
logging and monitoring.

And possibly people will still use unsupported war release to fulfill their
needs until Solr standalone release become stable.

For our use case we repackage solr war (maven release) to include some
custom code which help us to test/debug/deploy our code easily.

Most likely for us we have to create maven war artifact from solr.war
locally and publish to our internal maven repository, so our current build
and deploy process does not break.

On Tue, Feb 10, 2015 at 10:12 AM, Matt Kuiper <matt.kuiper@issinc.com>
wrote:

> Thanks for all the responses.  I am planning a new project, and
> considering deployment options at this time.  It's helpful to see where
> Solr is headed.
>
> Thanks,
>
> Matt Kuiper
>
> -----Original Message-----
> From: Shawn Heisey [mailto:apache@elyograg.org]
> Sent: Tuesday, February 10, 2015 10:05 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Solr on Tomcat
>
> On 2/10/2015 9:48 AM, Matt Kuiper wrote:
> > I am starting to look in to Solr 5.0.  I have been running Solr 4.* on
> Tomcat.   I was surprised to find the following notice on
> https://cwiki.apache.org/confluence/display/solr/Running+Solr+on+Tomcat
>  (Marked as Unreleased)
> >
> >      Beginning with Solr 5.0, Support for deploying Solr as a WAR in
> servlet containers like Tomcat is no longer supported.
> >
> > I want to verify that it is true that Solr 5.0 will not be able to run
> on Tomcat, and confirm that the recommended way to deploy Solr 5.0 is as a
> Linux service.
>
> Solr will eventually (hopefully soon) be entirely its own application.
> The documentation you have seen in the reference guide is there to prepare
> users for this eventuality.
>
> Right now we are in a transition period.  We have built scripts for
> controlling the start and stop of the example server installation.
> Under the covers, Solr is still a web application contained in a war and
> the example server still runs an unmodified copy of jetty.  Down the road,
> when Solr will becomes a completely standalone application, we will merely
> have to modify the script wrapper to use it, and the user may not even
> notice the change.
>
> With 5.0, if you want to run in tomcat, you will be able to find the war
> in the download's server/webapps directory and use it just like you do now
> ... but we will be encouraging people to NOT do this, because eventually it
> will be completely unsupported.
>
> Thanks,
> Shawn
>
>

--001a11343a4c7ac692050ec02d28--