You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/05/23 15:32:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16846790#comment-16846790 ]
ASF subversion and git services commented on LUCENE-8809:
---------------------------------------------------------
Commit 0435348b29ba25b15b01cf0a99ed3df7c205f294 in lucene-solr's branch refs/heads/master from Nhat Nguyen
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=0435348 ]
LUCENE-8809: Ensure release segment states
If refresh and rollback happen concurrently, then we can leave segment
states unreleased leads to leaking refCount of some SegmentReaders.
> 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
> Priority: Major
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org