Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of markrmiller@gmail.com
 designates 74.125.83.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=Xm+EgwC0EBtHdbnwlVzjHkV5EQZxI+SfxSTuqK3JDKC5nFOVktts6NgwQ6hSgWIMuf
         fM3tuQ5zTkZTpqo56yXjCRFCCfl7N6DuCUzjwYZ3+8gEc5vp9zpf1P3HFeqe0Lv7JD28
         f6qu04B0DoOCfFakFBe78lyuKYjbCFvFnVmbs=
Message-ID: <4C0FB0E7.9070109@gmail.com>
Date: Wed, 09 Jun 2010 08:19:03 -0700
From: Mark Miller <markrmiller@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: dev@lucene.apache.org
Subject: Re: Solr spewage and dropped documents, while indexing
References: <QWDzncttBPWx@8ddTbzvd>
 <CF3CE3EFBCA3564185DF065952A267C853445190D9@NOK-EUMSG-01.mgdnok.nokia.com>
 <4C0FA77A.7010708@gmail.com>
 <CF3CE3EFBCA3564185DF065952A267C853445191BD@NOK-EUMSG-01.mgdnok.nokia.com>
In-Reply-To: 
 <CF3CE3EFBCA3564185DF065952A267C853445191BD@NOK-EUMSG-01.mgdnok.nokia.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hang on though - I saw a commons jira issue from 08 that claimed the 
javadoc for this class was misleading and there was no default cleaner 
set - that issue was resolved, but the javadoc *still* seemed to 
indicate there was a default cleaner in use ... so I wondered if the 
code had changed, or the javadoc was still misleading ...

Looking at getFileCleaningTracker(), it also says:

An instance of FileCleaningTracker, defaults to FileCleaner.getInstance().

But then looking at the code, I don't see how that is possible. It 
really appears to default to null (no cleaner).

So I ran a quick test, printing out the cleaning tracker, and it prints 
'null'.

So, perhaps we try setting one and see where your problem is? It really 
appears the javadoc I'm seeing does not match the code.

- Mark

On 6/9/10 8:01 AM, karl.wright@nokia.com wrote:
> Ok, that theory bites the dust then...
>
> I'll have to work on some diagnostics then to see why the content doesn't get added.
>
> Karl
>
> -----Original Message-----
> From: ext Mark Miller [mailto:markrmiller@gmail.com]
> Sent: Wednesday, June 09, 2010 10:39 AM
> To: dev@lucene.apache.org
> Subject: Re: Solr spewage and dropped documents, while indexing
>
> On 6/9/10 6:01 AM, karl.wright@nokia.com wrote:
>>
>> but if I correctly recall how DiskFileItemFactory works, it creates
>> files and registers them to be cleaned up on JVM exit.  If that's the
>> only cleanup, that's not going to cut it for a real-world system.
>
> Class DiskFileItemFactory
>
> "Temporary files are automatically deleted as soon as they are no longer
> needed. (More precisely, when the corresponding instance of File is
> garbage collected.) Cleaning up those files is done by an instance of
> FileCleaningTracker, and an associated thread."
>


-- 
- Mark

http://www.lucidimagination.com

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