lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dawid Weiss <dawid.we...@cs.put.poznan.pl>
Subject Re: improving unique work.dir per JVM?
Date Sun, 23 Dec 2012 10:19:43 GMT
> I did RTFM.

Just joking.

> So dir=tempDir, be it java.io.tempdir or whatever you set when invoking ant.
> [snip]
> -DtempDir=/mnt/tmp/job1

There is a crucial difference. Lucene sets this to a temporary folder
underneath the checkout structure. So every checkout (as in a jenkins
plan or something) will have a different folder. The reason for
creating a sub-folder for the temporary junit4 files is the security
manager -- to allow all JVMs to write to the tempdir (that's how event
files are propagated to the master node for aggregation) and at the
same time disallow them to write anywhere else but their own current
working directory. So you end up with a folder structure like this:

parent/J0
parent/J1
parent/J[...]
parent/temp

the key for you is to isolate "parent" so you can't just point it to
the same folder across all JVMs. Whether you do this from ANT or from
command-line is up to you.

> I don't know why this mkdirs() didn't create the full path. I'm using the
> runner for Lucene 4.0, maybe it didn't call mkdirs() then?

I'm sure it does. Maybe it didn't have permissions or something? Or
maybe it wasn't the mkdirs that was the problem? Or maybe there's a
bug lurking somewhere. If you can reproduce it, file an issue, I'll
take a look.

D.

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


Mime
View raw message