lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3066) SolrIndexSearcher open/close imbalance in some of the new SolrCloud tests.
Date Wed, 08 Feb 2012 02:43:00 GMT


Mark Miller commented on SOLR-3066:

So a lot of this seemed to be fixed by adding a higher timeout when we wait for the searcher
open/close counts to balance out. I think this is partially because jenkins will run with
test multipliers and so some tests start and stop quite a few number of jetties, so it on
a slow system, it can take a little while for all cores to be released some times.

A couple of the tests that are currently ignored failed with bigger count mismatches though.
I didn't want to turn those back on without more assurance they might pass.

So I installed freebsd in virtualbox and started playing there within the confines of the
black hole behavior. I tried to run those two tests and indeed they failed - a couple stack
trace dumps and I realized that some recovery attempt calls where hanging - I had set timeouts
for the calls to recover/replicate, but not for the calls to sync. I added the timeouts and
those tests started passing.

So things are looking okay, except that i just saw that very rarely on jenkins, the zkrecovery
test is failing with an imbalance off by one. I'll probably make a different issue for that
less frequent case.
> SolrIndexSearcher open/close imbalance in some of the new SolrCloud tests.
> --------------------------------------------------------------------------
>                 Key: SOLR-3066
>                 URL:
>             Project: Solr
>          Issue Type: Test
>            Reporter: Mark Miller
> I have not been able to duplicate this test issue on my systems yet, but on jenkins,
some tests that start and stop jetty instances during the test are having trouble cleaning
up and can bleed into other tests. I'm working on isolating the reason for this - I seem to
have been ip banned from jenkins at the moment, but when I can ssh in there, I will be able
to speed up the try/feedback loop some. I've spent a lot of time trying to duplicate across
3 other systems, but I don't see the same issue anywhere but our jenkins server thus far.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message