In setup guide, I read
"Only Oracle’s Java and the OpenJDK are supported. The same JVM version
should be used on all Elasticsearch nodes and clients.
We recommend installing the Java 8 update 20 or later, or Java 7 update
55 or later. Previous versions of Java 7 are known to have bugs that can
cause index corruption and data loss."
We need to use IBM JVM due to company policy. Could you please tell me why
IBM JVM is not in your supported list? What symptoms are they when index
corruption and data loss happened? Any log trace to indicate that?
In setup guide, I read
"Only Oracle’s Java and the OpenJDK are supported. The same JVM version
should be used on all Elasticsearch nodes and clients.
We recommend installing the Java 8 update 20 or later, or Java 7
update 55 or later. Previous versions of Java 7 are known to have bugs
that can cause index corruption and data loss."
We need to use IBM JVM due to company policy. Could you please tell me why
IBM JVM is not in your supported list? What symptoms are they when index
corruption and data loss happened? Any log trace to indicate that?
I did read the page before. However, the section didn't mentioned any
details of the issue, not trace either. I was hoping some one has
experienced issues. Is just randomly happening or under certain conditions
to trigger index corruption?
On Wednesday, 28 January 2015 18:30:54 UTC-5, Mark Walkom wrote:
On 29 January 2015 at 09:56, 'Cindy' via elasticsearch < elasti...@googlegroups.com <javascript:>> wrote:
In setup guide, I read
"Only Oracle’s Java and the OpenJDK are supported. The same JVM version
should be used on all Elasticsearch nodes and clients.
We recommend installing the Java 8 update 20 or later, or Java 7
update 55 or later. Previous versions of Java 7 are known to have bugs
that can cause index corruption and data loss."
We need to use IBM JVM due to company policy. Could you please tell me
why IBM JVM is not in your supported list? What symptoms are they when
index corruption and data loss happened? Any log trace to indicate that?
There are known big installations using OpenJDK and Oracle JDK. I don't
know any using IBM. I imagine your more likely to find something on that
JDK then others but you'll probably do ok. Certainly be sure to add the
config parameter mentioned on that page and expect to have to fiddle with
the init script some.
I did read the page before. However, the section didn't mentioned any
details of the issue, not trace either. I was hoping some one has
experienced issues. Is just randomly happening or under certain conditions
to trigger index corruption?
On Wednesday, 28 January 2015 18:30:54 UTC-5, Mark Walkom wrote:
In setup guide, I read
"Only Oracle’s Java and the OpenJDK are supported. The same JVM version
should be used on all Elasticsearch nodes and clients.
We recommend installing the Java 8 update 20 or later, or Java 7
update 55 or later. Previous versions of Java 7 are known to have bugs
that can cause index corruption and data loss."
We need to use IBM JVM due to company policy. Could you please tell me
why IBM JVM is not in your supported list? What symptoms are they when
index corruption and data loss happened? Any log trace to indicate that?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.