Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 24 Sep 2015 21:49:04 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12895742.1443004169000.66873.1443131344598@Atlassian.JIRA>
In-Reply-To: <JIRA.12895742.1443004169000@Atlassian.JIRA>
References: <JIRA.12895742.1443004169000@Atlassian.JIRA>
 <JIRA.12895742.1443004169393@arcas>
Subject: [jira] [Commented] (LUCENE-6813) OfflineSorter.sort shouldn't
 remove the output Path up front
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF subversion and git services commented on LUCENE-6813:
---------------------------------------------------------

Commit 1705168 from [~mikemccand] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1705168 ]

LUCENE-6813: OfflineSorter no longer removes its output file up front; fix file handle leak in RangeTreeWriter

> OfflineSorter.sort shouldn't remove the output Path up front
> ------------------------------------------------------------
>
>                 Key: LUCENE-6813
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6813
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: Trunk, 5.4
>
>         Attachments: LUCENE-6813.patch, LUCENE-6813.patch, LUCENE-6813.patch
>
>
> The new BKD tree classes, and NumericRangeTree (just a 1D BKD tree),
> make heavy use of OfflineSorter to build their data structures at
> indexing time when the number of indexed documents is biggish.
> But when I was first building them (LUCENE-6477), I hit a thread
> safety issue in OfflineSorter, and at that time I just worked around
> it by creating my own private temp directory each time I need to write
> a BKD tree.
> This workaround is sort of messy, and it causes problems with "pending
> delete" files on Windows when we try to remove that temp directory,
> causing test failures like http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/5149/
> I think instead we should fix the root cause ... i.e. make
> OfflineSorter thread safe.  It looks like it's simple...
> Separately I'd like to somehow fix these BKD tests to catch any leaked
> file handles ... I'm not sure they are today.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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