[jira] [Resolved] (LUCENE-8809) Refresh and rollback concurrently can leave segment states unclosed
[ https://issues.apache.org/jira/browse/LUCENE-8809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nhat Nguyen resolved LUCENE-8809. - Resolution: Fixed [~simonw] Thanks for the ping. I have re-committed this to 8.1. > Refresh and rollback concurrently can leave segment states unclosed > --- > > Key: LUCENE-8809 > URL: https://issues.apache.org/jira/browse/LUCENE-8809 > Project: Lucene - Core > Issue Type: Bug > Components: core/index >Affects Versions: 7.7, 8.1, 8.2 >Reporter: Nhat Nguyen >Assignee: Nhat Nguyen >Priority: Major > Fix For: 7.7.2, master (9.0), 8.2, 8.1.2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > A [failed test|https://github.com/elastic/elasticsearch/issues/30290] from > Elasticsearch shows that refresh and rollback concurrently can leave segment > states unclosed leads to leaking refCount of some SegmentReaders. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Resolved] (LUCENE-8809) Refresh and rollback concurrently can leave segment states unclosed
[ https://issues.apache.org/jira/browse/LUCENE-8809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nhat Nguyen resolved LUCENE-8809. - Resolution: Fixed Assignee: Nhat Nguyen Fix Version/s: 8.2 master (9.0) 7.7.2 We need to commit this fix to 8_1 after the releasing of 8.1.1 completed. > Refresh and rollback concurrently can leave segment states unclosed > --- > > Key: LUCENE-8809 > URL: https://issues.apache.org/jira/browse/LUCENE-8809 > Project: Lucene - Core > Issue Type: Bug > Components: core/index >Affects Versions: 7.7, 8.1, 8.2 >Reporter: Nhat Nguyen >Assignee: Nhat Nguyen >Priority: Major > Fix For: 7.7.2, master (9.0), 8.2 > > Time Spent: 50m > Remaining Estimate: 0h > > A [failed test|https://github.com/elastic/elasticsearch/issues/30290] from > Elasticsearch shows that refresh and rollback concurrently can leave segment > states unclosed leads to leaking refCount of some SegmentReaders. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org