Thanks for your response. GC was my first thought too. I have looked
through the logs and ran the app through a profiler, I am not seeing any
spike in GC activity or any other background thread when performance
degrades. Also, the fact that the slowdown occurs exactly every minute at
the same
Have you run 'top' on the nodes?
On Wednesday, April 15, 2015 at 8:56:20 AM UTC-4, Daryl Robbins wrote:
Thanks for your response. GC was my first thought too. I have looked
through the logs and ran the app through a profiler, I am not seeing any
spike in GC activity or any other background
Thanks, Glen. Yes, I have run top: the Java Tomcat process is the only
thing running at the time. I also checked the thread activity in JProfiler
and nothing out of the ordinary popped up.
On Wednesday, April 15, 2015 at 1:36:55 PM UTC-4, Glen Smith wrote:
Have you run 'top' on the nodes?
Thank you, Glen. I appreciate your insight!
Here is our environment:
https://lh3.googleusercontent.com/-PLejC0Yt98I/VS7BDRa23pI/Ahk/MVoWqrRI8ls/s1600/ES%2BSetup.png
All nodes are running in a VPC within the same region of AWS, so inter-node
latency should be very minimal.
I was
Cool.
If I read right, your response time statistics graph includes
1 - network latency between the client nodes and the load balancer
2 - network latency between the load balancer and the cluster eligible
masters.
3 - performance of the load balancer
My interest in checking out 1 2 would
Well, it appears that this issue was actually unrelated to ElasticSearch
after all. The problem was actually between the API Load Balancer and the
API Server nodes. We are using ElasticBeanstalk, a managed application
container, to host these API nodes. It turns out the Apache configuration
Have you checked the logs for GC events or similar? What about the web logs
for events coming in?
On 15 April 2015 at 09:03, Daryl Robbins darylrobb...@gmail.com wrote:
I am seeing a consistent bottleneck in requests (taking about 2+ seconds)
at the same second every minute across all four of
I am seeing a consistent bottleneck in requests (taking about 2+ seconds)
at the same second every minute across all four of my client nodes who are
connecting using the transport client from Java. These nodes are completely
independent aside from their reliance on the ElasticSearch cluster
