[jira] [Updated] (SOLR-4858) UpdateLog not informed of core reload (leads to incorrect cores/update handlers being used)
[ https://issues.apache.org/jira/browse/SOLR-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-4858: --- Summary: UpdateLog not informed of core reload (leads to incorrect cores/update handlers being used) (was: updateLog + core reload + deleteByQuery = leaked directory) > UpdateLog not informed of core reload (leads to incorrect cores/update > handlers being used) > --- > > 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 >Assignee: Yonik Seeley > Fix For: 4.3.1 > > Attachments: find_leak.sh, 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-4858) UpdateLog not informed of core reload (leads to incorrect cores/update handlers being used)
[ https://issues.apache.org/jira/browse/SOLR-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-4858: --- Attachment: SOLR-4858_fix.patch Here's my fix (untested). I'll work on a test that hits this more directly. > UpdateLog not informed of core reload (leads to incorrect cores/update > handlers being used) > --- > > 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 >Assignee: Yonik Seeley > Fix For: 4.3.1 > > Attachments: find_leak.sh, SOLR-4858_fix.patch, 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-4858) UpdateLog not informed of core reload (leads to incorrect cores/update handlers being used)
[ https://issues.apache.org/jira/browse/SOLR-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-4858: --- Attachment: SOLR-4858_fix.patch Here's an updated fix that goes back to the way it worked before (init called at the end of the DUH2 constructor). Slightly messier, but slightly safer. > UpdateLog not informed of core reload (leads to incorrect cores/update > handlers being used) > --- > > 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 >Assignee: Yonik Seeley > Fix For: 4.3.1 > > Attachments: find_leak.sh, SOLR-4858_fix.patch, SOLR-4858_fix.patch, > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-4858) UpdateLog not informed of core reload (leads to incorrect cores/update handlers being used)
[ https://issues.apache.org/jira/browse/SOLR-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-4858: --- Attachment: SOLR-4858_fix.patch > UpdateLog not informed of core reload (leads to incorrect cores/update > handlers being used) > --- > > 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 >Assignee: Yonik Seeley > Fix For: 4.3.1 > > Attachments: find_leak.sh, SOLR-4858_fix.patch, SOLR-4858_fix.patch, > SOLR-4858_fix.patch, 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-4858) UpdateLog not informed of core reload (leads to incorrect cores/update handlers being used)
[ https://issues.apache.org/jira/browse/SOLR-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-4858: --- Attachment: SOLR-4858_fix.patch OK, hopefully the final patch that makes things fail faster by checking if the core is still open we open a new searcher. > UpdateLog not informed of core reload (leads to incorrect cores/update > handlers being used) > --- > > 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 >Assignee: Yonik Seeley > Fix For: 4.3.1 > > Attachments: find_leak.sh, SOLR-4858_fix.patch, SOLR-4858_fix.patch, > SOLR-4858_fix.patch, SOLR-4858_fix.patch, 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
