Yes it will, anything in the elasticsearch.yml that changes needs a restart.
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html
is the page that setting came from as well.
On 13 November 2014 08:38, shriyansh jain wrote:
>
> will it need a restart t
will it need a restart to being that info effect.?
Thank!
Shriyansh
On Wednesday, November 12, 2014 1:30:57 PM UTC-8, Mark Walkom wrote:
>
> You can add that in yourself.
>
> On 13 November 2014 08:26, shriyansh jain > wrote:
>
>> Thank you mark for pointing me out with the situation. As I am
Thanks!
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.goo
You can add that in yourself.
On 13 November 2014 08:26, shriyansh jain wrote:
> Thank you mark for pointing me out with the situation. As I am trying to
> delete the index I am getting timeouts for that. But you suggested me to
> increase discovery.zen.fd.ping_timeout to get rid of that. I am n
Thank you mark for pointing me out with the situation. As I am trying to
delete the index I am getting timeouts for that. But you suggested me to
increase discovery.zen.fd.ping_timeout to get rid of that. I am not able to
see any such variable in elasticsearch.yml file.
Can you please point me
You either need to add more nodes, reduce your dataset, increase the heap
or close some old indexes.
On 13 November 2014 08:11, shriyansh jain wrote:
> I am also getting Out of Memory exception now in the logs
>
> [2014-11-12 13:08:23,157][WARN ][netty.channel.DefaultChannelPipeline] An
> except
I am also getting Out of Memory exception now in the logs
[2014-11-12 13:08:23,157][WARN ][netty.channel.DefaultChannelPipeline] An
exception was thrown by a user handler while handling an exception event
([id: 0x40f3788c, /10.18.144.231:52924 => /10.18.144.229:9300] EXCEPTION:
java.lang.OutOfM
I have stopped collecting all the data from logstash( as I am using ELK
stack), but it still I am getting pretty large GC's (as you mentioned). Can
you please point me out what might be the reason for that.?
Thank you for the suggestion and pointing me out the error, I appreciate it
and will c
It won't solve it but it may help.
You have some pretty large GC's happening, some getting close to the 30s
default ping timeout.
You can try increasing discovery.zen.fd.ping_timeout but you may want to
consider adding another node in to generally help relieve heap pressure and
improve performance
Hi Mark,
The data is around id 150GB.
The master node holds : 16 GB RAM with ES_HEAP_SIZE = 8GB
The other node holds : 16 GB RAM with ES_HEAP_SIZE = 8 GB
I will get the version updated with Oracle Java, will that solve the issue.?
Thanks!
Shriyansh
--
You received this message because you ar
How much data is in the cluster? How big are your nodes?
You're running a very old version of Java, recommended is 1.7u55 or
greater, and Oracle not OpenJDK.
On 13 November 2014 06:49, shriyansh jain wrote:
> Hi all,
>
> I am getting timeout exceptions with elastic search while deleting an
> in
11 matches
Mail list logo
