[
https://issues.apache.org/jira/browse/SOLR-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-4858:
---------------------------
Attachment: SOLR-4858.patch
A much larger patch...
I initially found this bug because of a weird failure in a test i have on
dependent project, and it took me longer then i would have liked to reproduce
in a solr test because i didn't realize it was caused by using the updateLog,
and i didn't realize how few solr tests take advantage of the updateLog.
so with that in mind, it seemed to me like we should probably increase the test
coverage of hte updatLog to see if there are any more situations that tickle
bugs besides this odd edge case of reload+deleteByQuery.
so in this updated patch...
* same TestReloadAndDeleteDocs as before
* the test solrconfig.xml now defaults to using the updateLog
* SolrTestCaseJ4 uses randomization to occasionally disable the update log
with a sys property
* there is currently a nocommit in SolrTestCaseJ4 forcing the sys prop to
always be true
* any tests using solrconfig.xml that have an explicit need to use/not-use
updateLog override the sysprop explicitly
* a few schema files that did not have _version_ fields are updated to include
them
...this still only scratches the surface of increasing the test coverage for
the UpdateLog, but it already exposes a reproducible failure in AutoCommitTest
with the same symptoms as my TestReloadAndDeleteDocs...
* ERROR Timeout waiting for all directory ref counts...
* searcher leak.
(i have not yet narrowed down which method in AutoCommitTest the dir factory
ref count is lost in)
> updateLog + core reload + deleteByQuery = leaked directory
> ----------------------------------------------------------
>
> Key: SOLR-4858
> URL: https://issues.apache.org/jira/browse/SOLR-4858
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.2.1
> Reporter: Hoss Man
> Fix For: 4.3.1
>
> Attachments: SOLR-4858.patch, SOLR-4858.patch, SOLR-4858.patch
>
>
> I havene't been able to make sense of this yet, but trying to track down
> another bug lead me to discover that the following combination leads to
> problems...
> * updateLog enabled
> * do a core reload
> * do a delete by query \*:\*
> ...leave out any one of the three, and everything works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
