Just saw that the query profiler can not show what the shard execution times are, so maybe this is not a big help.
Jörg On Tue, Sep 16, 2014 at 9:24 AM, joergpra...@gmail.com < joergpra...@gmail.com> wrote: > If you are sure the spikes are caused by the JVM, I recommend to attach a > profiler to the JVM, then you can monitor the code. > > On JVM level, it is hard to trace queries, so maybe you want to test out > bleeding edge? Here is a query profiler: > https://github.com/elasticsearch/elasticsearch/pull/6699 > > Jörg > > On Tue, Sep 16, 2014 at 2:24 AM, Craig Wittenberg <crai...@microsoft.com> > wrote: > >> Hardware problems in Azure? Hmm. I suppose so :) >> >> In this case I restarted just ES (i.e., shutdown ES using >> http://localhost:9200/_cluster/nodes/_local/_shutdown and then ran >> elasticsearch.bat again) and thus didn't reboot the VM or anything so >> dramatic. All of the ES node files remained in place and the node >> reconnected with the cluster with no issue. My rdp session remained. I >> suspect if this were a hardware issue a) we would have seen this long ago >> and b) it would have persisted after I restarted ES. >> >> Related, we actually have two clusters of the same size and same data >> that have exhibited the same behavior. The cluster in which I restarted >> three ES nodes remains responsive. The other cluster in which I have not >> (yet) restarted nodes remains with the highly variable response time >> (200-40000ms with 34415ms being a recent one). >> >> Thanks for replying. >> >> Craig. >> >> On Monday, September 15, 2014 2:58:22 PM UTC-7, Jörg Prante wrote: >> >>> You said you restarted a node, and since then, the effect has gone, is >>> that true? Such high spikes like 40sec response might indicate problems in >>> the hardware (disk failure, network latency or timeout, DNS), is this >>> possible? >>> >>> 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+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/9d74b9a8-cdcc-474f-9a34-9e2fa8240c74%40googlegroups.com >> <https://groups.google.com/d/msgid/elasticsearch/9d74b9a8-cdcc-474f-9a34-9e2fa8240c74%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHmfhQXKpPp5uPszVsp-zoHkE3s_v%3DnZUw0b9w%3DMr_-WA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
