Noble Paul നോബിള് नोब्ळ् schrieb:
These logs were added to warn us developers on some missing cleanups.
Doing cleanups in finalize() is not considered clean.
It should not cause any harm other than those nasty messages.
that's what I thought because I didn't experience any problems. But
doesn't that indicate that there is a missing cleanup?
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'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.
Cheers,
Chantal
On Fri, Nov 6, 2009 at 4:59 AM, markwaddle <m...@markwaddle.com> wrote:
For what it's worth, I have encountered this error in the logs nearly once a
day for the last 3 weeks. It appears so often, yet so inconsistently that it
does not seem to occur while performing a specific operation or near a
specific error.
Mark
Chantal Ackermann wrote:
Hi all,
just wanted to post this log output because it has 3 exclamation marks
which makes it sound important. ;-)
It has happened after an index process on one core was rolled back. The
select request in between was issued on a different core.
I have seen this message before but also only after some exception
happened. I just reindexed successfully (no rollback) and no SEVERE
reappeared.
Otherwise everything works fine, so I suppose it's more a matter of log
message placement / log level choice etc.
Cheers,
Chantal
05.11.2009 16:13:23 org.apache.solr.update.DirectUpdateHandler2 rollback
INFO: start rollback
05.11.2009 16:13:23 org.apache.solr.update.DirectUpdateHandler2 rollback
INFO: end_rollback
05.11.2009 16:14:33 org.apache.solr.core.SolrCore execute
INFO: [sei] webapp=/solr path=/dataimport params={} status=0 QTime=9
05.11.2009 16:43:38 org.apache.solr.core.SolrCore execute
INFO: [epg] webapp=/solr path=/select
params={sort=start_date+asc,start_date+asc&start=0&q=%2Bstart_date:[*+TO+NOW]+%2Bend_date:[NOW+TO+*]+%2Bruntime:[5+TO+300]&wt=javabin&rows=20&version=1}
hits=8 status=0 QTime=297
05.11.2009 17:10:25 org.apache.solr.update.SolrIndexWriter finalize
SEVERE: SolrIndexWriter was not closed prior to finalize(), indicates a
bug -- POSSIBLE RESOURCE LEAK!!!
--
View this message in context:
http://old.nabble.com/SEVERE%3A-SolrIndexWriter-was-not-closed-prior-to-finalize-tp26217896p26224126.html
Sent from the Solr - Dev mailing list archive at Nabble.com.
