Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I am using master-slave in redis. So when master goes down the slave become new master and when the old master comes up it becomes slave for new master. So i want to know wheather there is a way that whenever the original master comes up again instead of becoming slave it should become master and new master shld become slave. So is this possible?? #3620

Closed
brishi19791 opened this issue Nov 18, 2016 · 2 comments

Comments

@brishi19791
Copy link

No description provided.

@brishi19791 brishi19791 changed the title I am using master-slave in redis. So when master goes down the slave become new master and when the old master comes up it becomes slave for new master. So i want to know wheather there is a way that whenever the original master comes up again instead of becoming slave it should become master and new master shld become slave? I am using master-slave in redis. So when master goes down the slave become new master and when the old master comes up it becomes slave for new master. So i want to know wheather there is a way that whenever the original master comes up again instead of becoming slave it should become master and new master shld become slave. So is this possible?? Nov 18, 2016
@cbgbt
Copy link
Contributor

cbgbt commented Dec 1, 2016

Hi @brishi19791

I don't have the know-how to answer your question, but I did see this bit when I was perusing the CONTRIBUTING file.

You might have better luck asking on the subreddit or stackoverflow.

@badboy
Copy link
Contributor

badboy commented Dec 1, 2016

To answer the question: no, there is no automatic way. You could trigger a failover once the old master is back. However, additional failovers are often not what you really want.

Apart from that:
Keep in mind that this issue tracker should be used for bugs or improvements to the Redis server. For questions like yours please ask on /r/redis, the mailing list or ask in the irc channel #redis on freenode.

@badboy badboy closed this as completed Jul 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants