CODEWITHSUNDEEP
amazon-web-servicesmemcachedamazon-elasticachespymemcached
filippo.derosa84
filippo.derosa84

Reputation: 126

AWS Elasticache backed by memcached CPU usage flat line at 1%

I've created an ElastiCache cluster in AWS, with node type as t3.micro (500 MB, 2 vCPUs and network up to 5 gigabit). My current setup is having 3 nodes for High Availability, each node is in a different AZ.

I'm using the AWS labs memcached client for Java (https://github.com/awslabs/aws-elasticache-cluster-client-memcached-for-java) that allows auto discovery of nodes, i.e. I only need to provide the cluster DNS record and the client will automatically discover all nodes within that cluster.

I intermittently get some timeout errors:

1) Error in custom provider, net.spy.memcached.OperationTimeoutException: Timeout waiting for value: waited 2,500 ms. Node status: Connection Status { /XXX.XX.XX.XXX:11211 active: false, authed: true, last read: 44,772 ms ago /XXX.XX.XX.XXX:11211 active: true, authed: true, last read: 4 ms ago /XXX.XX.XX.XXX:11211 active: true, authed: true, last read: 6 ms ago

I'm trying to understand what's the problem, but nothing really stands out by looking at the CloudWatch metrics.

The only thing that looks a bit weird is the CPU utilization graph: CPU utilization graph

The CPU always maxes out at 1% during peak hours, so I'm trying to understand how to read this value and whether this is not a 1% but more of a 100%, indicating that there's a bottleneck on the CPU.

Any help on this?

Upvotes: 1

Views: 596

Answers (1)

Leandro Donizetti Soares
Leandro Donizetti Soares

Reputation: 492

Just one question. Why are using such small instances? How is the memory use. My guess is the same as yours. The CPU is causing the trouble. 3 micro instances are not much. I would try to increase the instances. But it is just a guess.

Upvotes: 0

Related Questions