lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LUCENE-5574) NRT Reader close can wipe index it doesn't own
Date Fri, 04 Apr 2014 08:45:16 GMT
Simon Willnauer created LUCENE-5574:
---------------------------------------

             Summary: NRT Reader close can wipe index it doesn't own
                 Key: LUCENE-5574
                 URL: https://issues.apache.org/jira/browse/LUCENE-5574
             Project: Lucene - Core
          Issue Type: Bug
          Components: core/index
    Affects Versions: 4.7.1, 4.8, 5.0
            Reporter: Simon Willnauer
            Priority: Critical
             Fix For: 4.8, 5.0


Today NRT Readers try to clean up unused files via their IW reference when they are closed.
Yet, if the index writer is already closed another index could have been created on the same
directory which can create the same files as the IW before. For the NRT Reader those files
are not referenced and it will simply wipe them away. If you use this in a replication scenario
where directories are reused this can simply wipe your index away or in combination with the
FSync issue LUCENE-5570 create 0-byte files. I have a test that reproduces this issue



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message