Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
Originally, the sun.misc.Cleaner interface was declared as "critical API" in JEP 260
Unfortunately the decission was changed in favor of a oficially supported java.lang.ref.Cleaner API. A side effect of this change is to move all existing sun.misc.Cleaner APIs into a non-exported package. This causes our forceful unmapping to no longer work, because we can get the cleaner instance via reflection, but trying to invoke it will throw one of the new Jigsaw RuntimeException because it is completely inaccessible. This will make our forceful unmapping fail. There are also no changes in Garbage collector, the problem still exists.
For more information see this mailing list thread.
This commit will likely be done, making our unmapping efforts no longer working. Alan Bateman is aware of this issue and will open a new issue at OpenJDK to allow forceful unmapping without using the now private sun.misc.Cleaner. The idea is to let the internal class sun.misc.Cleaner implement the Runable interface, so we can simply cast to runable and call the run() method to unmap. The code would then work. This will lead to minor changes in our unmapper in MMapDirectory: An instanceof check and casting if possible.
I opened this issue to keep track and implement the changes as soon as possible, so people will have working unmapping when java 9 comes out. Current Lucene versions will no longer work with Java 9.
Attachments
Attachments
Issue Links
- is related to
-
HADOOP-12760 sun.misc.Cleaner has moved to a new location in OpenJDK 9
- Resolved
-
LUCENE-10342 Add (very limited) java.util.logging to Lucene Core
- Closed
-
LUCENE-8154 TODO List when upgrading to Java 9 as minimum requirement
- Resolved
- relates to
-
LUCENE-7595 RAMUsageTester in test-framework and static field checker no longer works with Java 9
- Resolved
-
LUCENE-7596 Update Groovy to 2.4.8 in build system
- Resolved