Redis Sentinel elects a new master node

Sentinel elects a new master node, but the associated master/slave configuration information is not persisted to redis.conf Error message in redis.conf:

* MASTER MODE enabled
# Could not rename tmp config file (Device or resource busy)
# CONFIG REWRITE failed: Device or resource busy

I have granted read and write permission to redis.conf, and there is no occupation, so I wonder why these configurations cannot be persisted

Comment From: moticless

Hi @CarlosShao2, Sentinel rewrite the configuration file from the very start. Does the message happen from the beginning? Most probably it is an environment issue, such as file system permissions or multiple sentinel wrongly attempt to use the same configuration file. Please lookup first for known utilities, such as ‘lsof’ to further isolate this issue and let us know if you still think it is Redis issue.

Thank you.