Resolution
----------

Unexpected node restarts, performance issues, and nodes in recovery mode might happen when your DAX cluster performs maintenance updates [during its maintenance window](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.concepts.cluster.html#DAX.concepts.maintenance-window). It's a best practice to [customize your maintenance window](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.cluster-management.html#DAX.cluster-management.custom-settings) to a time when you experience the least traffic. Also, turn on Amazon Simple Notification Service (Amazon SNS) notifications for DAX maintenance events. Through notifications, you receive up-to-date information about your DAX cluster's status.

Related information
-------------------

[How can I troubleshoot high latency on Amazon DynamoDB Accelerator (DAX) clusters?](https://repost.aws/knowledge-center/high-latency-dax-clusters)

[How do I troubleshoot a "No endpoints available" error in the DAX client?](https://repost.aws/knowledge-center/fix-endpoint-error-dax)

[How do I troubleshoot a "ThrottlingException" with Amazon DynamoDB Accelerator (DAX) operations?](https://repost.aws/knowledge-center/fix-dax-throttling)

A node in my Amazon DynamoDB Accelerator (DAX) cluster unexpectedly restarts in recovery mode. When the node restarts, I experience issues such as SocketTimeouts, Throttling, or “No Endpoints Available” exceptions. I want to resolve this issue.

Understand why DAX nodes restart in recovery mode

Why do my DAX nodes suddenly restart in recovery mode?

Database

Troubleshooting managed node issues in Systems Manager with SAW

How do I troubleshoot a “No endpoints available” error in the DAX client?

Why is the core node in my Amazon EMR cluster running out of disk space?

How do I choose the appropriate instance type and node size for my ElastiCache for Redis self-designed cluster?

How can I troubleshoot high latency on DynamoDB Accelerator (DAX) clusters?

parallelcluster: nfs performance and cluster scalability - head node unresponsive

selecting node type & number of nodes of redshift cluster only from a performance perspective

DAX errors in log - NoRouteException: not able to resolve address

Pods running in EKS cluster cannot initialize due to aws-node restarting possibly pointing at cni issues

DAX performance results are the same as with dynamodb

Why do my DAX nodes suddenly restart in recovery mode?

Resolution

Related information

Relevant content