Hi Jack,
On 4/27/07, Jack L <[EMAIL PROTECTED]> wrote:
...Is there a build script that automagically grab files from jetty's
source tree (local) and build a solr release? In other words, I can
try building with a newer version of jetty if it doesn't take too
much work - I don't know much about j
Hello Bertrand,
Is there a build script that automagically grab files from jetty's
source tree (local) and build a solr release? In other words, I can
try building with a newer version of jetty if it doesn't take too
much work - I don't know much about jetty or solr at the code level.
--
Best re
- Original Message
From: Erik Hatcher <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Wednesday, April 25, 2007 4:26:41 PM
Subject: Re: Re[4]: Things are not quite stable...
On Apr 25, 2007, at 3:27 PM, Mike Klaas wrote:
> On 4/25/07, Jack L <[EMAIL PROTECTED]> wr
On 4/25/07, Jack L <[EMAIL PROTECTED]> wrote:
...Regardless, I think it's a good idea to use a newer, released (not RC)
version in general, considering 5.1 is one major version behind
Agreed, but note that we don't have any factual evidence that the
Jetty RC that we use is indeed the cause
On 4/25/07, Jack L <[EMAIL PROTECTED]> wrote:
I don't know for sure. But from the symptom, when error 404 happens,
solr seems to still work fine (so does that part of Jetty.) Then those
404'ed pages may have some solr specific logic in it?
I'm really not sure--I've built several long-running,
On Apr 25, 2007, at 3:27 PM, Mike Klaas wrote:
On 4/25/07, Jack L <[EMAIL PROTECTED]> wrote:
That is understood.
For people who are not familiar with Java servlet containers, like
myself, the embedded web server takes the least effort to set up.
And jetty is supposed be a production quality q
Mike,
I don't know for sure. But from the symptom, when error 404 happens,
solr seems to still work fine (so does that part of Jetty.) Then those
404'ed pages may have some solr specific logic in it?
Regardless, I think it's a good idea to use a newer, released (not RC)
version in general, consid
On 4/25/07, Jack L <[EMAIL PROTECTED]> wrote:
That is understood.
For people who are not familiar with Java servlet containers, like
myself, the embedded web server takes the least effort to set up.
And jetty is supposed be a production quality quality package, it'll be
great that the default pa
That is understood.
For people who are not familiar with Java servlet containers, like
myself, the embedded web server takes the least effort to set up.
And jetty is supposed be a production quality quality package, it'll be
great that the default package with jetty can be used for production.
--
On 4/25/07, Jack L <[EMAIL PROTECTED]> wrote:
> Are you running a Solr release, or a snapshot? It'd be interesting to
> know If you're running code that predates the fix done in SOLR-173. In
> my case, on the production system the code is older than that.
I'm running the 1.1.0 release.
Maybe i
On 4/25/07, Jack L <[EMAIL PROTECTED]> wrote:
...Maybe it's time to think about upgrading Jetty...
It's in the pipeline, see https://issues.apache.org/jira/browse/SOLR-128
-Bertrand
Hello Bertrand,
>> ...solr stops functioning properly after running for a few days.
>> The symptom is search returning nothing, or when I go to /solr/admin/,
>> I get file browsing page showing a list of files (.css, etc),...
> Are your symptoms similar to those of
> https://issues.apache.org/jir
On 4/25/07, Jack L <[EMAIL PROTECTED]> wrote:
...solr stops functioning properly after running for a few days.
The symptom is search returning nothing, or when I go to /solr/admin/,
I get file browsing page showing a list of files (.css, etc),...
Are your symptoms similar to those of
https://i
I'm running the default solr package with my data, about 10 million
small documents. I'm not sure if it's jetty or solr, but often
times solr stops functioning properly after running for a few days.
The symptom is search returning nothing, or when I go to /solr/admin/,
I get file browsing page sh
14 matches
Mail list logo
