If you use sentinel to manage two master and two slave databases, in the form of one master-to-one slave, which php connection should be used for writing content, currently the connection sentinel cannot be written. The idea is as follows: when php directly connects to sentinel, sentinel serves as the server, but sentinel does not support conventional redis commands such as set ,... if you use sentinel to manage two master and two slave databases, in the form of one master-to-one slave, which php connection should be used for writing content, currently the connection sentinel cannot be written.
The idea is as follows:
When php directly connects to sentinel, sentinel serves as the server, but sentinel does not support conventional redis commands such as set, so it should not be connected to redis sentinel,
If php directly connects to the master server, sentinel will switch from the master server to the master server after the master server crashes. php cannot switch over in real time.
I have never encountered this problem before. Could you share your solutions or ideas? Thank you in advance.
Reply content:
If you use sentinel to manage two master and two slave databases, in the form of one master-to-one slave, which php connection should be used for writing content, currently the connection sentinel cannot be written.
The idea is as follows:
When php directly connects to sentinel, sentinel serves as the server, but sentinel does not support conventional redis commands such as set, so it should not be connected to redis sentinel,
If php directly connects to the master server, sentinel will switch from the master server to the master server after the master server crashes. php cannot switch over in real time.
I have never encountered this problem before. Could you share your solutions or ideas? Thank you in advance.