`ElasticSearch will note in its normal logs if any GC is happening which
effects a slow query, but we wanted more detail. Another logging option
ElasticSearch has is ES_USE_GC_LOGGING which sets some JVM variables:
from elasticsearch.in.sh.erbif [ "x$ES_USE_GC_LOGGING" != "x" ]; then
`Elasticsearch will note in its normal logs if any GC is happening which
effects a slow query, but we wanted more detail. Another logging option
Elasticsearch has is ES_USE_GC_LOGGING which sets some JVM variables:
from elasticsearch.in.sh.erbif [ "x$ES_USE_GC_LOGGING" != "x" ]; then
Can you please tell me what exactly do I need to add in
/etc/default/elasticsearch?
What should I set ES_USE_GC_LOGGING to?
I added below line in my dev ES node, and I didn't see the gc.log file in
my log folder.. I want to be sure what to do before changing anything in my
production cluster..
ES_USE_GC_LOGGING=true
And what are the GC logging options in my elasticsearch.yml do? where do
those logs appear?
Thank you.
On Wednesday, March 4, 2015 at 3:11:26 AM UTC+5:30, Mark Walkom wrote:
You can set JAVA_OPTS in /etc/default/elasticsearch or
/etc/sysconfig/elasticsearch u9nder ES_JAVA_OPTS
On 3 March 2015 at 23:11, Anil Karaka <anilk...@gmail.com <javascript:>>
wrote:
Some of the nodes are leaving the cluster from time to time..
I un commented the GC Logging options in elasticsearch.yml file as shown
and restarted my node.
`Elasticsearch will note in its normal logs if any GC is happening which
effects a slow query, but we wanted more detail. Another logging option
Elasticsearch has is ES_USE_GC_LOGGING which sets some JVM variables:
from elasticsearch.in.sh.erbif [ "x$ES_USE_GC_LOGGING" != "x" ]; then
On Wednesday, March 4, 2015 at 9:22:50 AM UTC-5, Anil Karaka wrote:
Can you please tell me what exactly do I need to add in
/etc/default/elasticsearch?
What should I set ES_USE_GC_LOGGING to?
I added below line in my dev ES node, and I didn't see the gc.log file in
my log folder.. I want to be sure what to do before changing anything in my
production cluster..
ES_USE_GC_LOGGING=true
And what are the GC logging options in my elasticsearch.yml do? where do
those logs appear?
Thank you.
On Wednesday, March 4, 2015 at 3:11:26 AM UTC+5:30, Mark Walkom wrote:
You can set JAVA_OPTS in /etc/default/elasticsearch or
/etc/sysconfig/elasticsearch u9nder ES_JAVA_OPTS
`Elasticsearch will note in its normal logs if any GC is happening
which effects a slow query, but we wanted more detail. Another logging
option Elasticsearch has is ES_USE_GC_LOGGING which sets some JVM
variables:
from elasticsearch.in.sh.erbif [ "x$ES_USE_GC_LOGGING" != "x" ]; then
I just kept those GC logging options outside the if block.. So that I don't
have to set that variable, and enabled GC logging by default.
this is in the file /usr/share/elasticsearch/bin/elasticsearch.in.sh
GC logging options
if [ "x$ES_USE_GC_LOGGING" != "x" ]; then
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCDetails"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCTimeStamps"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintClassHistogram"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintTenuringDistribution"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCApplicationStoppedTime"
JAVA_OPTS="$JAVA_OPTS -Xloggc:/var/log/elasticsearch/gc.log"
fi
On Wednesday, March 4, 2015 at 9:22:50 AM UTC-5, Anil Karaka wrote:
Can you please tell me what exactly do I need to add in
/etc/default/elasticsearch?
What should I set ES_USE_GC_LOGGING to?
I added below line in my dev ES node, and I didn't see the gc.log file in
my log folder.. I want to be sure what to do before changing anything in my
production cluster..
ES_USE_GC_LOGGING=true
And what are the GC logging options in my elasticsearch.yml do? where do
those logs appear?
Thank you.
On Wednesday, March 4, 2015 at 3:11:26 AM UTC+5:30, Mark Walkom wrote:
You can set JAVA_OPTS in /etc/default/elasticsearch or
/etc/sysconfig/elasticsearch u9nder ES_JAVA_OPTS
`Elasticsearch will note in its normal logs if any GC is happening
which effects a slow query, but we wanted more detail. Another logging
option Elasticsearch has is ES_USE_GC_LOGGING which sets some JVM
variables:
from elasticsearch.in.sh.erbif [ "x$ES_USE_GC_LOGGING" != "x" ]; then
I just kept those GC logging options outside the if block.. So that I
don't have to set that variable, and enabled GC logging by default.
this is in the file /usr/share/elasticsearch/bin/elasticsearch.in.sh
GC logging options
if [ "x$ES_USE_GC_LOGGING" != "x" ]; then
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCDetails"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCTimeStamps"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintClassHistogram"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintTenuringDistribution"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCApplicationStoppedTime"
JAVA_OPTS="$JAVA_OPTS -Xloggc:/var/log/elasticsearch/gc.log"
fi
On Wednesday, March 4, 2015 at 9:22:50 AM UTC-5, Anil Karaka wrote:
Can you please tell me what exactly do I need to add in
/etc/default/elasticsearch?
What should I set ES_USE_GC_LOGGING to?
I added below line in my dev ES node, and I didn't see the gc.log file
in my log folder.. I want to be sure what to do before changing anything in
my production cluster..
ES_USE_GC_LOGGING=true
And what are the GC logging options in my elasticsearch.yml do? where do
those logs appear?
Thank you.
On Wednesday, March 4, 2015 at 3:11:26 AM UTC+5:30, Mark Walkom wrote:
You can set JAVA_OPTS in /etc/default/elasticsearch or
/etc/sysconfig/elasticsearch u9nder ES_JAVA_OPTS
`Elasticsearch will note in its normal logs if any GC is happening
which effects a slow query, but we wanted more detail. Another logging
option Elasticsearch has is ES_USE_GC_LOGGING which sets some JVM
variables:
from elasticsearch.in.sh.erbif [ "x$ES_USE_GC_LOGGING" != "x" ]; then
Ok, we also had to edit that file to change the default garbage collector
options and are now using G1GC. So I thought I will just change the if
condition to enable gc logs..
Any way, this is not the main problem, I'm trying to do all these things to
debug the main issue of my nodes leaving the cluster randomly. Redirecting to Google Groups here are
more details. Any help would be appreciated.
Yesterday night I increased the zen.ping.timeout from 3s to 10s of all my
machines and restarted them one by one, and yet to see if its any
improvement.
Will updating elasticsearch in my nodes fix my issues? Currently my nodes
are using ES-1.4.1.
Thanks.
On Thursday, April 2, 2015 at 3:02:31 AM UTC+5:30, Mark Walkom wrote:
It's not recommended to alter the .in.sh, this file can change between
releases and your alterations can either be lost or can cause other
problems.
I'd suggest you do what Gavin mentioned.
On 1 April 2015 at 18:08, Anil Karaka <anilk...@gmail.com <javascript:>>
wrote:
Thanks,
I just kept those GC logging options outside the if block.. So that I
don't have to set that variable, and enabled GC logging by default.
this is in the file /usr/share/elasticsearch/bin/elasticsearch.in.sh
GC logging options
if [ "x$ES_USE_GC_LOGGING" != "x" ]; then
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCDetails"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCTimeStamps"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintClassHistogram"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintTenuringDistribution"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCApplicationStoppedTime"
JAVA_OPTS="$JAVA_OPTS -Xloggc:/var/log/elasticsearch/gc.log"
fi
On Wednesday, March 4, 2015 at 9:22:50 AM UTC-5, Anil Karaka wrote:
Can you please tell me what exactly do I need to add in
/etc/default/elasticsearch?
What should I set ES_USE_GC_LOGGING to?
I added below line in my dev ES node, and I didn't see the gc.log file
in my log folder.. I want to be sure what to do before changing anything in
my production cluster..
ES_USE_GC_LOGGING=true
And what are the GC logging options in my elasticsearch.yml do? where
do those logs appear?
Thank you.
On Wednesday, March 4, 2015 at 3:11:26 AM UTC+5:30, Mark Walkom wrote:
You can set JAVA_OPTS in /etc/default/elasticsearch or
/etc/sysconfig/elasticsearch u9nder ES_JAVA_OPTS
`Elasticsearch will note in its normal logs if any GC is happening
which effects a slow query, but we wanted more detail. Another logging
option Elasticsearch has is ES_USE_GC_LOGGING which sets some JVM
variables:
from elasticsearch.in.sh.erbif [ "x$ES_USE_GC_LOGGING" != "x" ]; then
Ok, we also had to edit that file to change the default garbage collector
options and are now using G1GC. So I thought I will just change the if
condition to enable gc logs..
Any way, this is not the main problem, I'm trying to do all these things
to debug the main issue of my nodes leaving the cluster randomly. Redirecting to Google Groups here
are more details. Any help would be appreciated.
Yesterday night I increased the zen.ping.timeout from 3s to 10s of all my
machines and restarted them one by one, and yet to see if its any
improvement.
Will updating elasticsearch in my nodes fix my issues? Currently my nodes
are using ES-1.4.1.
Thanks.
On Thursday, April 2, 2015 at 3:02:31 AM UTC+5:30, Mark Walkom wrote:
It's not recommended to alter the .in.sh, this file can change between
releases and your alterations can either be lost or can cause other
problems.
I just kept those GC logging options outside the if block.. So that I
don't have to set that variable, and enabled GC logging by default.
this is in the file /usr/share/elasticsearch/bin/elasticsearch.in.sh
GC logging options
if [ "x$ES_USE_GC_LOGGING" != "x" ]; then
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCDetails"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCTimeStamps"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintClassHistogram"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintTenuringDistribution"
JAVA_OPTS="$JAVA_OPTS -XX:+PrintGCApplicationStoppedTime"
JAVA_OPTS="$JAVA_OPTS -Xloggc:/var/log/elasticsearch/gc.log"
fi
On Wednesday, March 4, 2015 at 9:22:50 AM UTC-5, Anil Karaka wrote:
Can you please tell me what exactly do I need to add in
/etc/default/elasticsearch?
What should I set ES_USE_GC_LOGGING to?
I added below line in my dev ES node, and I didn't see the gc.log file
in my log folder.. I want to be sure what to do before changing anything in
my production cluster..
ES_USE_GC_LOGGING=true
And what are the GC logging options in my elasticsearch.yml do? where
do those logs appear?
Thank you.
On Wednesday, March 4, 2015 at 3:11:26 AM UTC+5:30, Mark Walkom wrote:
You can set JAVA_OPTS in /etc/default/elasticsearch or
/etc/sysconfig/elasticsearch u9nder ES_JAVA_OPTS
`Elasticsearch will note in its normal logs if any GC is happening
which effects a slow query, but we wanted more detail. Another logging
option Elasticsearch has is ES_USE_GC_LOGGING which sets some JVM
variables:
from elasticsearch.in.sh.erbif [ "x$ES_USE_GC_LOGGING" != "x" ]; then
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.