which example? there are so many.
On Wed, Nov 13, 2013 at 1:00 PM, Mark Miller wrote:
> RE: the example folder
>
> It’s something I’ve been pushing towards moving away from for a long time -
> see https://issues.apache.org/jira/browse/SOLR-3619 Rename 'example' dir to
> 'server' and pull exampl
RE: the example folder
It’s something I’ve been pushing towards moving away from for a long time - see
https://issues.apache.org/jira/browse/SOLR-3619 Rename 'example' dir to
'server' and pull examples into an 'examples’ directory
Part of a push I’ve been on to own the Container level (people a
On 11/13/2013 5:29 AM, Dmitry Kan wrote:
Reading that people have considered deploying "example" folder is slightly
strange to me. No wonder they are confused and confuse their ops.
I do use the stripped jetty included in the example, but my setup is not
a straight copy of the example director
Hi,
Reading that people have considered deploying "example" folder is slightly
strange to me. No wonder they are confused and confuse their ops. We just
took vanilla jetty (jetty9) and installed solr.war on it, configured it, no
example folders at all. Since then it works nicely.
The main reason
So, it sounds like that either Solr is treated as a webapp, in which case
it is installed with most of the webapps under Tomcat (legacy/operational
reason). So, Solr docs just needs to explain how to deploy under Tomcat and
the rest of document/tooling comes from Tomcat community.
Or, if Solr is t
My case is also similar to "Sujit Pal" but we have jboss6.
On Tue, Nov 12, 2013 at 9:47 AM, Sujit Pal wrote:
> In our case, it is because all our other applications are deployed on
> Tomcat and ops is familiar with the deployment process. We also had
> customizations that needed to go in, so we
In our case, it is because all our other applications are deployed on
Tomcat and ops is familiar with the deployment process. We also had
customizations that needed to go in, so we inserted our custom JAR into the
solr.war's WEB-INF/lib directory, so to ops the process of deploying Solr
was (almost
On 11/12/2013 09:28 AM, Lukasz Salwinski wrote:
On 12.11.13 04:54, Alexandre Rafalovitch wrote:
Hello,
I keep seeing here and on Stack Overflow people trying to deploy
Solr to Tomcat. We don't usually ask why, just help when where we can.
But the question happens often enough that I am curious
On 12.11.13 04:54, Alexandre Rafalovitch wrote:
Hello,
I keep seeing here and on Stack Overflow people trying to deploy
Solr to Tomcat. We don't usually ask why, just help when where we can.
But the question happens often enough that I am curious. What is the
actual business case. Is that becau
Hi ALex,
in my case
* ignorance that Tomcat is not fully supported
* Tomcat configuration and operations know-how inhouse
* could migrate to Jetty but need approved change request to do so
Cheers,
Siegfried Goeschl
On 12.11.13 04:54, Alexandre Rafalovitch wrote:
Hello,
I keep seeing here an
iscussed - the views can help me
> argue our case to use jetty if it is indeed more beneficial to do so.
>
> Gil
>
> -Original Message-
> From: Sebastián Ramírez [mailto:sebastian.rami...@senseta.com]
> Sent: 12 November 2013 13:38
> To: solr-user@lucene.apache.org
>
o use jetty if it is indeed more beneficial to do so.
Gil
-Original Message-
From: Sebastián Ramírez [mailto:sebastian.rami...@senseta.com]
Sent: 12 November 2013 13:38
To: solr-user@lucene.apache.org
Subject: Re: Why do people want to deploy to Tomcat?
I agree with Doug, when I started I had to sp
g discussed - the views can help me argue our
case to use jetty if it is indeed more beneficial to do so.
Gil
-Original Message-
From: Sebastián Ramírez [mailto:sebastian.rami...@senseta.com]
Sent: 12 November 2013 13:38
To: solr-user@lucene.apache.org
Subject: Re: Why do people want to deplo
I agree with Doug, when I started I had to spend some time figuring out
what was just an "example" and what I would have to change in a
"production" environment... until I found that all the "example" was ready
for production.
Of course, you commonly have to change the settings, parameters, fields
Agreed with Doug
On 12-Nov-2013 6:46 PM, "Doug Turnbull"
wrote:
> As an aside, I think one reason people feel compelled to deviate from the
> distributed jetty distribution is because the folder is named "example".
> I've had to explain to a few clients that this is a bit of a misnomer. The
> IT
As an aside, I think one reason people feel compelled to deviate from the
distributed jetty distribution is because the folder is named "example".
I've had to explain to a few clients that this is a bit of a misnomer. The
IT dept especially sees "example" and feels uncomfortable using that as a
sta
I personally felt Tomcat to be in a more appropriate community, that of the
Apache Foundation, than Jetty.
Also, jetty always has been striving for simplicity and that's really not
always what you intend to when you plan an app-server.
E.g. features such as the manager or mod_ajp appeared import
In my case, the first time I had to deploy and configure solr on tomcat
(and jboss) it was a requirement to reuse as much as possible the
application/web server already in place. The next deployment I also use
tomcat, because I was used to deploy on tomcat and I don't know jetty at
all.
I could as
In my case, the selection of the servlet container has never been a hard
requirement. I mean, some customers provide us a virtual machine configured
with java/tomcat , others have a tomcat installed and want to share it with
solr, others prefer jetty because their sysadmins are used to configure
it
We are using Solr running on Tomcat.
I think the top reasons for us are :
- we already have nagios monitoring plugins for tomcat that trace
queries ok/error, http codes / response time etc in access logs, number
of threads, jvm memory usage etc
- start, stop, watchdogs, logs : we also use our s
20 matches
Mail list logo
