Java 1.7u25 did not improve the situation. The java-client still
fork-bombed.
Any other ideas for what we can try? Any ideas why it might happen?
--
Magnus Haug
On Monday, March 17, 2014 10:52:37 AM UTC+1, mag...@stack.no wrote:
Yes I can try downgrading as an experiment, getting to it ASAP.
System info:
Elasticsearch 0.90.7.
$ cat /etc/issue
Red Hat Enterprise Linux Server release 6.4 (Santiago)
Kernel \r on an \m$ cat /etc/lsb-release
LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
$ java -version
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)--
Magnus HaugOn Saturday, March 15, 2014 11:49:51 AM UTC+1, Jörg Prante wrote:
I understand Java HotSpot(TM) 64-Bit Server VM (24.51-b03 mixed mode -
this is Java 7u51 on OS Mavericks? If so can you downgrade to 7u25?Jörg
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9b10f75c-97a8-47ce-8879-1ba6d3cb721e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.