Re: how often do you boys restart your tomcat?

2011-07-27 Thread Bernd Fehling

Till now I used jetty and got 2 week as the longest uptime until OOM.
I just switched to tomcat6 and will see how that one behaves but
I think its not a problem of the servlet container.
Solr is pretty unstable if having a huge database.
Actually this can't be blamed directly to Solr it is a problem of
Lucene and its fieldCache. Somehow during 2 weeks runtime with searching
and replication the fieldCache gets doubled until OOM.

Currently there is no other solution to this than restarting your
tomcat or jetty regularly :-(


Am 27.07.2011 03:42, schrieb Bing Yu:

I find that, if I do not restart the master's tomcat for some days,
the load average will keep rising to a high level, solr become slow
and unstable, so I add a crontab to restart the tomcat everyday.

do you boys restart your tomcat ? and is there any way to avoid restart tomcat?


Re: how often do you boys restart your tomcat?

2011-07-27 Thread Paul Libbrecht
On curriki.org, our solr's Tomcat saturates memory after 2-4 weeks.
I am still investigating if I am accumulating something or something else is.

To check it, I am running a query all, return num results every minute to 
measure the time it takes. It's generally when it meets a big GC that gives a 
timeout that I start to worry. Memory then starts to be hogged but things get 
back to normal as soon as the GC is out.

I had other tomcat servers with very long uptimes (more than 6 months) so I do 
not think tomcat is guilty.

Currently I can only show the freememory of the system and what's in 
solr-stats, but I do not know what to look at really...

paul

Le 27 juil. 2011 à 03:42, Bing Yu a écrit :

 I find that, if I do not restart the master's tomcat for some days,
 the load average will keep rising to a high level, solr become slow
 and unstable, so I add a crontab to restart the tomcat everyday.
 
 do you boys restart your tomcat ? and is there any way to avoid restart 
 tomcat?



Re: how often do you boys restart your tomcat?

2011-07-27 Thread Bernd Fehling


It is definately Lucenes fieldCache making the trouble.
Restart your solr and monitor it with jvisualvm, especially OldGen heap.
When it gets to 100 percent filled use jmap to dump heap of your system.
Then use Eclipse Memory Analyzer http://www.eclipse.org/mat/ and
open the heap dump. You will see a pie chart and can easily identify
the largets consumer of your heap space.



Am 27.07.2011 09:02, schrieb Paul Libbrecht:

On curriki.org, our solr's Tomcat saturates memory after 2-4 weeks.
I am still investigating if I am accumulating something or something else is.

To check it, I am running a query all, return num results every minute to 
measure the time it takes. It's generally when it meets a big GC that gives a timeout 
that I start to worry. Memory then starts to be hogged but things get back to normal as 
soon as the GC is out.

I had other tomcat servers with very long uptimes (more than 6 months) so I do 
not think tomcat is guilty.

Currently I can only show the freememory of the system and what's in 
solr-stats, but I do not know what to look at really...

paul

Le 27 juil. 2011 à 03:42, Bing Yu a écrit :


I find that, if I do not restart the master's tomcat for some days,
the load average will keep rising to a high level, solr become slow
and unstable, so I add a crontab to restart the tomcat everyday.

do you boys restart your tomcat ? and is there any way to avoid restart tomcat?




how often do you boys restart your tomcat?

2011-07-26 Thread Bing Yu
I find that, if I do not restart the master's tomcat for some days,
the load average will keep rising to a high level, solr become slow
and unstable, so I add a crontab to restart the tomcat everyday.

do you boys restart your tomcat ? and is there any way to avoid restart tomcat?


Re: how often do you boys restart your tomcat?

2011-07-26 Thread Chamnap Chhorn
I often restarted the tomcat service before the memory reaches the os limit.
Usually, it eats up only 4 GB, but eventually it eats up 11GB.

On Wed, Jul 27, 2011 at 8:42 AM, Bing Yu icedf...@gmail.com wrote:

 I find that, if I do not restart the master's tomcat for some days,
 the load average will keep rising to a high level, solr become slow
 and unstable, so I add a crontab to restart the tomcat everyday.

 do you boys restart your tomcat ? and is there any way to avoid restart
 tomcat?




-- 
Chhorn Chamnap
http://chamnapchhorn.blogspot.com/


Re: how often do you boys restart your tomcat?

2011-07-26 Thread Dave Hall

On 27/07/11 11:42, Bing Yu wrote:

do you boys restart your tomcat ? and is there any way to avoid restart tomcat?


Our female sysadmin takes care of managing our server.


Re: how often do you boys restart your tomcat?

2011-07-26 Thread Bing Yu
I want to let system do the job instead of system adminm, beause I'm lazy ~ ^__^

But I just want a better way to fix the problem. restart server will
cause some other problem like I need to rebuild the changes happened
during the restart.

2011/7/27 Dave Hall dave.h...@skwashd.com:
 On 27/07/11 11:42, Bing Yu wrote:

 do you boys restart your tomcat ? and is there any way to avoid restart
 tomcat?

 Our female sysadmin takes care of managing our server.



Re: how often do you boys restart your tomcat?

2011-07-26 Thread Shawn Heisey

On 7/26/2011 7:42 PM, Bing Yu wrote:

I find that, if I do not restart the master's tomcat for some days,
the load average will keep rising to a high level, solr become slow
and unstable, so I add a crontab to restart the tomcat everyday.

do you boys restart your tomcat ? and is there any way to avoid restart tomcat?


I run Solr under the jetty included with the Solr examples.  With Solr 
version 1.4.1, I've had over 60 days of uptime with no problem.  I am 
now running 3.2.0, but things have been pretty volatile so I haven't 
been able to accumulate any real uptime yet.  I don't expect any 
problems, though.


Tomcat is something I've got little experience with, but that does sound 
unusual.  Other groups in the company do use it.  When they start having 
problems like this, it tends to be configuration issues, a bug in their 
homegrown applications, or a problem with resources (usually RAM).


Shawn