Request for Assistance with Amazon ElastiCache Redis UNCERTAIN_STATE Issue

During a specific timeframe, we noticed that our application logs indicated the status of our Amazon ElastiCache Redis cluster as UNCERTAIN_STATE.

As a workaround to restore functionality, we performed a reboot of the ElastiCache nodes in both instances. It is worth noting that even the redis flushall command was ineffective until the nodes were rebooted.

We need assistance in investigating the root cause of this UNCERTAIN_STATE status [ whether it's an underlying infrastructure or corrupted data or connection release ] and providing guidance on preventing such occurrences in the future.

Note: The connected_clients value was 71 when the issue had occurred.