Yes, you should use this option. Some FreeBSD kernels seem to have difficulties to run UDP multicast on IPv6 together with IPv4 properly, so I would like to suggest disabling IPv6 use on the JVM.
Jörg On Fri, May 2, 2014 at 10:23 AM, Patrick Proniewski < [email protected]> wrote: > Hi Jörg, > > Thank you for your reply. > The service script includes an option that might deal with IPv6, but it's > not active: > > # Force the JVM to use IPv4 stack > # elasticshearch_props"-Djava.net.preferIPv4Stack=true" > > (< > http://svnweb.freebsd.org/ports/head/textproc/elasticsearch/files/elasticsearch.in?revision=349955 > >) > > In past years, I used to disable IPv6 everywhere (kernel, ports > compilation, etc.) but now I don't bother anymore. > Do you mean I should use this option to force IPv4? > > Thanks, > Patrick > > > On 2 mai 2014, at 09:38, [email protected] wrote: > > > On FreeBSD, do you have multicast on IPv6 enabled? You should disable > IPv6 > > on the JVM. > > > > Seems you received a severe network error from the OS. > > > > Jörg > > > > > > On Thu, May 1, 2014 at 11:46 PM, Patrick Proniewski < > > [email protected]> wrote: > > > >> Hello, > >> > >> I'm running a small server with logstash, ES, Kibana. Tonight, I've > >> restarted my ES process. Very bad idea: it restarted with lots of > errors, > >> and finally "lost" all its data. > >> Basically, before restart, I've had: > >> > >> elasticsearch/nodes/0/indices/logstash-2014.* > >> elasticsearch/nodes/0/_state/ > >> > >> after restart, I've had: > >> > >> elasticsearch/nodes/0/indices/logstash-2014.* > >> elasticsearch/nodes/0/_state/ > >> elasticsearch/nodes/1/indices/logstash-2014.05.01 > >> elasticsearch/nodes/1/_state/ > >> > >> Then, Kibana was not able to find anything (dashboards lost, etc.). > >> > >> I've stopped Logstash, stopped Elasticsearch, waited a bit and checked > >> everything is down, then restarted ES. It looked OK, then I've restarted > >> Logstash, and I was able to access my dashboards again. I've just lost > 15 > >> minutes of data. > >> Now I can see that elasticsearch/nodes/0 is the current working > directory, > >> and I can browse old data and current data. > >> elasticsearch/nodes/1 is not used anymore. > >> > >> I'm running FreeBSD, and used the service command to restart ES. When > >> attempting the second shutdown, the script wouldn't find the pid file, > so > >> I've had to kill the Java process. > >> > >> I don't understand what happened. But I don't feel comfortable putting > ES > >> in production. Full log for first and second restart here: < > >> http://patpro.net/elastic.log> > >> > >> Any idea? > >> Regards, > >> Patrick > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/AA0BC7BA-8856-4A23-A172-0601BC0B4FEE%40patpro.net > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGN_zdUi9cCAoAgprBh-Lxtu_g1ejSQWT_nZU0fd_YRTA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
