Solr 5.x deployment in production

[Steven White <sw...@gmail.com>]

Hi folks,

With Solr 5.0, the WAR file is deprecated and I see Jetty is included with
Solr.  What if I have my own Web server into which I need to deploy Solr,
how do I go about doing this correctly without messing things up and making
sure Solr works?  Or is this not recommended and Jetty is the way to go, no
questions asked?

Thanks

Steve

Re: Solr 5.x deployment in production

[Steven White <sw...@gmail.com>]

Thanks Shawn, this makes a lot of sense.

With WAR going away and no mention of Solr deployment strategy (see:
https://cwiki.apache.org/confluence/display/solr/Taking+Solr+to+Production)
isn't good; there is a gab in Solr's release. It feels as if Solr 5.x was
rushed out ignoring Windows Servers deployment.

-- George

On Fri, Apr 17, 2015 at 9:24 AM, Shawn Heisey <ap...@elyograg.org> wrote:

> On 4/16/2015 2:07 PM, Steven White wrote:
> > In my case, I have to deploy Solr on Windows, AIX, and Linux (all server
> > edition).  We are a WebSphere shop, moving away from it means I have to
> > deal with politics and culture.
>
> You *can* run Solr 5.0 (and 5.1) in another container, just like you
> could with all previous Solr versions.  There are additional steps that
> have to be taken, such as correctly installing the logging jars and the
> logging config, but if you've used Solr 4.3 or later, you already know
> this:
>
> http://wiki.apache.org/solr/SolrLogging
>
> Eventually, hopefully before we reach the 6.0 release, that kind of
> deployment won't be possible, because Solr will be a true application
> (like Jetty itself), not a webapp contained in a .war file.  It may take
> us quite a while to reach that point.  If you are already using the
> scripts that come with Solr 5.x, you will have a seamless transition to
> the new implementation.
>
> The docs for 5.0 say that we aren't supporting deployment in a
> third-party servlet container, even though that still is possible.
> There are several reasons for this:
>
> * Eventually it won't be possible, because Solr's implementation will
> change.
>
> * We now have scripts that will start Solr in a consistent manner.
> ** This means that our instructions won't have to change for a new
> implementation.
>
> * There are a LOT of containers available.
> ** Each one requires different instructions.
> ** Are problems caused by the container, or Solr?  We may not know.
>
> * Jetty is the only container that gets tested.
> ** Bugs with other containers have happened.
> ** User feedback is usually the only way such bugs can be found.
>
> Thanks,
> Shawn
>
>

Re: Solr 5.x deployment in production

[Shawn Heisey <ap...@elyograg.org>]

On 4/16/2015 2:07 PM, Steven White wrote:
> In my case, I have to deploy Solr on Windows, AIX, and Linux (all server
> edition).  We are a WebSphere shop, moving away from it means I have to
> deal with politics and culture.

You *can* run Solr 5.0 (and 5.1) in another container, just like you
could with all previous Solr versions.  There are additional steps that
have to be taken, such as correctly installing the logging jars and the
logging config, but if you've used Solr 4.3 or later, you already know this:

http://wiki.apache.org/solr/SolrLogging

Eventually, hopefully before we reach the 6.0 release, that kind of
deployment won't be possible, because Solr will be a true application
(like Jetty itself), not a webapp contained in a .war file.  It may take
us quite a while to reach that point.  If you are already using the
scripts that come with Solr 5.x, you will have a seamless transition to
the new implementation.

The docs for 5.0 say that we aren't supporting deployment in a
third-party servlet container, even though that still is possible. 
There are several reasons for this:

* Eventually it won't be possible, because Solr's implementation will
change.

* We now have scripts that will start Solr in a consistent manner.
** This means that our instructions won't have to change for a new
implementation.

* There are a LOT of containers available.
** Each one requires different instructions.
** Are problems caused by the container, or Solr?  We may not know.

* Jetty is the only container that gets tested.
** Bugs with other containers have happened.
** User feedback is usually the only way such bugs can be found.

Thanks,
Shawn

Re: Solr 5.x deployment in production

[Steven White <sw...@gmail.com>]

Thanks Karl.

In my case, I have to deploy Solr on Windows, AIX, and Linux (all server
edition).  We are a WebSphere shop, moving away from it means I have to
deal with politics and culture.

For Windows, I cannot use NSSM so I have to figure a solution managing Solr
(at least start-up and shutdown).  If anyone has experience in this area
(now that Solr is not in a WAS profile managed by Windows services) and can
share your experience, please do.  Thanks.

Steve

On Thu, Apr 16, 2015 at 3:49 PM, Karl Kildén <ka...@gmail.com> wrote:

> I asked a very similar question recently. You should switch to using the
> package as is and forget that it contains a .war. The war is now an
> internal component. Also switch to the new script for startup etc.
>
> I have seen several disappointed users that disagree with this decision but
> I assume the project now has more freedom in the future and also more
> alignment and focus on one experience.
>
> I did my own thing with NSSM because we use windows and I am satisfied.
>
> On 16 April 2015 at 21:36, Steven White <sw...@gmail.com> wrote:
>
> > Hi folks,
> >
> > With Solr 5.0, the WAR file is deprecated and I see Jetty is included
> with
> > Solr.  What if I have my own Web server into which I need to deploy Solr,
> > how do I go about doing this correctly without messing things up and
> making
> > sure Solr works?  Or is this not recommended and Jetty is the way to go,
> no
> > questions asked?
> >
> > Thanks
> >
> > Steve
> >
>

Re: Solr 5.x deployment in production

[Karl Kildén <ka...@gmail.com>]

I asked a very similar question recently. You should switch to using the
package as is and forget that it contains a .war. The war is now an
internal component. Also switch to the new script for startup etc.

I have seen several disappointed users that disagree with this decision but
I assume the project now has more freedom in the future and also more
alignment and focus on one experience.

I did my own thing with NSSM because we use windows and I am satisfied.

On 16 April 2015 at 21:36, Steven White <sw...@gmail.com> wrote:

> Hi folks,
>
> With Solr 5.0, the WAR file is deprecated and I see Jetty is included with
> Solr.  What if I have my own Web server into which I need to deploy Solr,
> how do I go about doing this correctly without messing things up and making
> sure Solr works?  Or is this not recommended and Jetty is the way to go, no
> questions asked?
>
> Thanks
>
> Steve
>