: that's what I thought because I didn't experience any problems. But doesn't
: that indicate that there is a missing cleanup?

yes, it does.

: And if it is not worth checking / changing then maybe the log level should be
: decreased to adjust in comparison to other SEVERE warnings?

it really is an indication of a severe problem -- but unfortunately it's 
an indication of a problem detected during GC, which was was dealt with.  
the reason it's classified as SEVERE is because it's possible whatever 
caused this problem may be resulting in a resource leak which is *not* 
being detected.

It would be really helpful if people seeing these messages frequently in 
their logs could elaborate a little bit more on...

1) exactly which version/build of Solr they are using
2) whether they have any custom plugins loaded (either that they developed 
on their own, or from a third party, or even from solr/contrib)
3) what types of funtionality of Solr they use when dealing with 
indexing (ie: DIH, CSV loading, Solr Cell, SignatureUpdateProcessor, 
etc...)

Because this problem is only detected during GC, the log messages arround 
when it happens are probably not directly helpful, but a better picture of 
the *pattern* of behaviors that trigger this would be very helpful.

The one thing i do notice in particular about the log messages that were 
posted in this thread is that the rollback feature was used ... is this a 
common pattern? ... do all of the people noticing these "POSSIBLE RESOURCE 
LEAK" messages use rollback?  is there any correlation between how much 
you use rollback and how often you get one of these messages? (even if 
they don't happen at/near the same times)

: It's just that monitoring systems will of course raise an alarm on SEVERE
: messages. And even if SOLR runs perfect these messages would give the
: impression that something's going wrong.

(solr isn't running perfectly, and something is goig wrong, but luckily 
it's going wrong in a way that solr can recover from ... it could just as 
easily go wrong in a way that solr can't recover from)



-Hoss

Reply via email to