After redis stores sessions, redis sometimes dies. What is the problem?

Our current project uses redis to store sessions. The customer said that the login was not successful the day before yesterday. After checking, we found that redis was not working and restarted redis. Today, this problem occurs again, what is the possible cause? How can this problem be solved? Our current project uses redis to store sessions. The customer said that the login was not successful the day before yesterday. After checking, we found that redis was not working and restarted redis. Today, this problem occurs again,
What is the possible cause? How can this problem be solved?

Reply content:

Our current project uses redis to store sessions. The customer said that the login was not successful the day before yesterday. After checking, we found that redis was not working and restarted redis. Today, this problem occurs again,
What is the possible cause? How can this problem be solved?

There are many reasons. Let's take a look at this article and analyze it against your specific scenarios:
Http://www.oschina.net/translate/redis-latency-problems-troubleshooting? Lang = chs & page = 1 #

If phpredis is used as a session, do not enable persistence. It will consume the sock handler of the hot third party and the server.

Insufficient memory?

It may be that the Session Handler mechanism provided by the PECL extension phpredis is deadlocked, resulting in a single-thread Redis to have no response directly.

According to your situation, most of the reasons may be that the socket is exhausted because the resources are not released.