Enhanced safety of Lucene directory reader locker
by Anuj Shah
Hello,
When using the Lucene directory in production we have encountered many
instances of files being removed incorrectly.
After much investigation, we found issues and logged:
- ISPN-4497 <https://issues.jboss.org/browse/ISPN-4497>
- ISPN-4777 <https://issues.jboss.org/browse/ISPN-4777>
After a long period of stability, we've still found rare problems, relating
to when applications are shutdown. I don't need to go into the details here.
We've now decided rather than trying to fix the problems we would enhance
the DistributedSegmentReadLocker to prevent unwarranted file deletes. The
mechanism is quite simple, in that when the directory really wants a file
deleted we would add an additional marker to the cache and then proceed
with a real delete only if this marker is present. You can see the changes
here:
https://github.com/anujshahwork/infinispan/commit/a31e93cee452549e8820f72...
Would appreciate feedback on this idea and whether we should create a
feature request along with pull request.
Thanks
Anuj Shah
10 years, 12 months
Special cache types and their configuration (or lack of)
by Tristan Tarrant
Hi all,
I wanted to bring attention to some discussion that has happened in the
context of Radim's work on simplified code for specific cache types [1].
In particular, Radim proposes adding explicit configuration options
(i.e. a new simple-cache cache type) to the programmatic/declarative API
to ensure that a user is aware of the limitations of the resulting cache
type (no interceptors, no persistence, no tx, etc).
My opinion is that we should aim for "less" configuration and not
"more", and that optimizations such as these should get enabled
implicitly when the parameters allow it: if the configuration code
detects it can use a "simple" cache.
Also, this choice should happen at cache construction time, and not
dynamically at cache usage time.
WDYT ?
Tristan
[1] https://github.com/infinispan/infinispan/pull/3577
--
Tristan Tarrant
Infinispan Lead
JBoss, a division of Red Hat
11 years
Early Access builds for JDK 8u60 b26 and JDK 9 b75 are available on java.net
by Rory O'Donnell
Hi Galder,
Early Access build for JDK 8u60 b26 <http://jdk8.java.net/download.html>
is available on java.net, summary of changes are listed here.
<http://download.java.net/jdk8u60/changes/jdk8u60-b26.html?q=download/jdk8...>
As we enter the later phases of development for JDK 8u60, please log any
show stoppers as soon as possible.
Early Access build for JDK 9 b75 <https://jdk9.java.net/download/> is
available on java.net, summary of changes are listed here
<http://download.java.net/jdk9/changes/jdk9-b75.html?q=download/jdk9/chang...>.
With respect to ongoing JDK 9 development, there are two new Candidate
JEPs I'd like to draw your attention to.
Firstly, Mark Reinhold has put forward JEP 260: Encapsulate Most
Internal APIs to make most of the JDK's internal APIs inaccessible by
default but leave a few critical, widely-used internal APIs accessible,
until supported replacements exist for all or most of their functionality.
You can find the JEP here: http://openjdk.java.net/jeps/260 - and an
introductory e-mail and discussion thread on the OpenJDK jigsaw-dev
mailing list, starting at
http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-August/004433.html .
If you would like to provide additional feedback, please join the
jigsaw-dev mailing list, and contribute to the discussion there.
Secondly, Mandy Chung has put forward JEP 259: Stack-Walking API to
define an efficient standard API for stack walking that allows easy
filtering of, and lazy access to, the information in stack traces. You
can find the JEP here: http://openjdk.java.net/jeps/259 .
If you would like to provide feedback on JEP 259, please join the
OpenJDK core-libs-dev mailing list and contribute to the discussion there.
Finally, we are looking for feedback via a survey on Java Style
Guidelines Please see here for more details.
http://mail.openjdk.java.net/pipermail/discuss/2015-August/003766.html
Rgds, Rory
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
11 years
Question about Hibernate ORM 5.0 + Infinispan 8.0...
by Scott Marlow
Hi,
I heard that Infinispan 8.0 may soon be integrated into WildFly 10.0.
If that happens, how does that impact Hibernate ORM 5.0 which currently
integrates with Infinispan 7.2.1.Final? Does Hibernate ORM 5.0 need any
changes to integrate with Infinispan 8.0?
Thanks,
Scott
11 years
