lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Commented] (LUCENE-8809) Refresh and rollback concurrently can leave segment states unclosed
Date Tue, 28 May 2019 11:04:00 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-8809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849602#comment-16849602
] 

Jan Høydahl commented on LUCENE-8809:
-------------------------------------

[~dnhatn] your commits lack a {{lucene/CHANGES.txt}} entry.

> 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: 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message