I believe this issue is related to this Jetty bug report:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=357318
Gili
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-3-3-crashes-after-18-hours-tp3218496p3655937.html
Sent from the Solr - User mailing list archive at
Am 10.08.2011 17:11, schrieb Yonik Seeley:
On Wed, Aug 10, 2011 at 11:00 AM, alexander sulza.s...@digiconcept.net wrote:
Okay, with this command it hangs.
It doesn't look like a hang from this thread dump. It doesn't look
like any solr requests are executing at the time the dump was taken.
Am 19.08.2011 15:48, schrieb alexander sulz:
Am 10.08.2011 17:11, schrieb Yonik Seeley:
On Wed, Aug 10, 2011 at 11:00 AM, alexander
sulza.s...@digiconcept.net wrote:
Okay, with this command it hangs.
It doesn't look like a hang from this thread dump. It doesn't look
like any solr requests
On Fri, Aug 19, 2011 at 10:36 AM, alexander sulz a.s...@digiconcept.net wrote:
using lsof I think I pinned down the problem: too many open files!
I already doubled from 512 to 1024 once but it seems there are many SOCKETS
involved,
which are listed as can't identify protocol, instead of real
Am 19.08.2011 16:43, schrieb Yonik Seeley:
On Fri, Aug 19, 2011 at 10:36 AM, alexander sulza.s...@digiconcept.net wrote:
using lsof I think I pinned down the problem: too many open files!
I already doubled from 512 to 1024 once but it seems there are many SOCKETS
involved,
which are listed as
Hi, googling hotspot server 19.1-b02 shows that you are not alone
with hanging threads and crashes. And not only with solr.
Maybe try another JAVA?
Bernd
Am 10.08.2011 17:00, schrieb alexander sulz:
Okay, with this command it hangs.
Also: I managed to get a Thread Dump (attached).
regards
I know it seems like my problem may not be the same as the original
poster, but in investigating this, I did find this Jetty issue that
may be related: http://jira.codehaus.org/browse/JETTY-1377
Stephen Duncan Jr
www.stephenduncanjr.com
On Thu, Aug 4, 2011 at 1:54 PM, Stephen Duncan Jr
Okay, with this command it hangs.
Also: I managed to get a Thread Dump (attached).
regards
Am 05.08.2011 15:08, schrieb Yonik Seeley:
On Fri, Aug 5, 2011 at 7:33 AM, alexander sulza.s...@digiconcept.net wrote:
Usually you get a XML-Response when doing commits or optimize, in this case
I get
On Wed, Aug 10, 2011 at 11:00 AM, alexander sulz a.s...@digiconcept.net wrote:
Okay, with this command it hangs.
It doesn't look like a hang from this thread dump. It doesn't look
like any solr requests are executing at the time the dump was taken.
Did you do this from the command line?
curl
Usually you get a XML-Response when doing commits or optimize, in this
case I get nothing
in return, but the site ( http://[...]/solr/update?optimize=true )
DOESN'T load forever or anything.
It doesn't hang! I just get a blank page / empty response.
I use the stuff in the example folder, the
On Fri, Aug 5, 2011 at 7:33 AM, alexander sulz a.s...@digiconcept.net wrote:
Usually you get a XML-Response when doing commits or optimize, in this case
I get nothing
in return, but the site ( http://[...]/solr/update?optimize=true ) DOESN'T
load forever or anything.
It doesn't hang! I just
Thank you for the many replies!
Like I said, I couldn't find anything in logs created by solr.
I just had a look at the /var/logs/messages and there wasn't anything
either.
What I mean by crash is that the process is still there and http GET
pings would return 200
but when i try visiting
On Thu, Aug 4, 2011 at 8:09 AM, alexander sulz a.s...@digiconcept.net wrote:
Thank you for the many replies!
Like I said, I couldn't find anything in logs created by solr.
I just had a look at the /var/logs/messages and there wasn't anything
either.
What I mean by crash is that the process
Check out Physcial memory/virtual memory usage.
RAM usage might be less but Physical memory usage goes up as you index more
documents.
It might be because of MMapDirectory which used MappedByteBuffer.
On Thu, Aug 4, 2011 at 7:38 PM, Yonik Seeley yo...@lucidimagination.comwrote:
On Thu, Aug 4,
On Thu, Aug 4, 2011 at 10:08 AM, Yonik Seeley
yo...@lucidimagination.com wrote:
ignores means what? The request hangs? If so, could you get a thread dump?
Do queries work (like /solr/select?q=*:*) ?
thous throwing no errors, no 503's.. It's like the server has a blackout and
stares
Hello folks,
I'm using the latest stable Solr release - 3.3 and I encounter strange
phenomena with it.
After about 19 hours it just crashes, but I can't find anything in the
logs, no exceptions, no warnings,
no suspicious info entries..
I have an index-job running from 6am to 8pm every 10
Any JAVA_OPTS set?
Do not use -XX:+OptimizeStringConcat or -XX:+AggressiveOpts flags.
Am 02.08.2011 12:01, schrieb alexander sulz:
Hello folks,
I'm using the latest stable Solr release - 3.3 and I encounter strange
phenomena with it.
After about 19 hours it just crashes, but I can't find
Nope, none :/
Am 02.08.2011 12:33, schrieb Bernd Fehling:
Any JAVA_OPTS set?
Do not use -XX:+OptimizeStringConcat or -XX:+AggressiveOpts flags.
Am 02.08.2011 12:01, schrieb alexander sulz:
Hello folks,
I'm using the latest stable Solr release - 3.3 and I encounter
strange phenomena with
Strange, anything out of the ordinary in the syslog?
On Tuesday 02 August 2011 12:01:35 alexander sulz wrote:
Hello folks,
I'm using the latest stable Solr release - 3.3 and I encounter strange
phenomena with it.
After about 19 hours it just crashes, but I can't find anything in the
logs,
What do you mean by it just crashes? Does the process stops execution? Does
it takes too long to respond which might result in lots of 503s in your
application? Does the system run out of resources?
Are you indexing and serving from the same server? It happened once with us
that Solr was
Monitor your memory usage. I use to encounter a problem like this before
where nothing was in the logs and the process was just gone.
Turned out my system was out odd memory and swap got used up because of
another process which then forced the kernel to start killing off processes.
Google OOM
Assuming you are running on Linux, you might want to check /var/log/messages
too (the location might vary), I think the kernel logs forced process
termination there. I recall that the kernel will usually picks the process
consuming the most memory, there may be other factors involved too.
22 matches
Mail list logo
