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

Multiple Redis-Proxy #15

Open
tutunci opened this issue Feb 2, 2013 · 7 comments
Open

Multiple Redis-Proxy #15

tutunci opened this issue Feb 2, 2013 · 7 comments

Comments

@tutunci
Copy link

tutunci commented Feb 2, 2013

Hi,
is there any possibile configuration to have two active redis-proxy connected to the same redis group instead of an HA by keepalived or ElasticIP configuration?
I mean why can't be two different servers running redis-proxy, the only issue is about how to manage master and slave on redis side.
Any idea about it?

Thanks,
Maurizio

@sreeix
Copy link
Owner

sreeix commented Feb 6, 2013

Hi,
it is slightly hard, there are couple of options i am looking at, but i will post a solution soon.(next week ?)

Cheers
sreekanth

@tutunci
Copy link
Author

tutunci commented Feb 6, 2013

Great!!!
Thank you

@tutunci
Copy link
Author

tutunci commented Mar 15, 2013

Hi sreeix,
Did you have some time to evaluate this improuve request?

Thanks
Maurizio

@sreeix
Copy link
Owner

sreeix commented Mar 19, 2013

Yes, I have pushed changes that make master resolution consistent, this was a prerequisite for the above request. it is on master now, I'd like to take some help from you in testing it. If that is ok?
I also want to know what your setup is so that I can try and replicate it here.

Cheers
sreekanth.

@tutunci
Copy link
Author

tutunci commented Mar 19, 2013

Hi Sreekanth,
thanks a lot!!!
I'm going to upload my sandbox.

I'm currently working on a Job Scheduler that manage time scheduled activities.
Everything is stored into Redis (2.4.17 version) with a master-slave environment.
Some are simple key-value data and some are key with score.
A daemon continuously check into key with score (timestamp is the score) if there is something to do; so a lot of calls are made ​​to Redis.
This environment must be fault tolerant so everything is duplicated.

I'll start some tests soon and update you.

Bye bye
Maurizio

@derekorgan
Copy link

Hey,

I'm right in the middle of trying to implement a no single point of failure and automated failover solution. Have you guys got this working?

Derek

@sreeix
Copy link
Owner

sreeix commented May 3, 2013

Hi Derek,
I have tested it and it works well. Give it a shot and let me know how it
goes.

On Thu, May 2, 2013 at 9:13 PM, Derek Organ [email protected]:

Hey,

I'm right in the middle of trying to implement a no single point of
failure and automated failover solution. Have you guys got this working?

Derek


Reply to this email directly or view it on GitHubhttps://github.com//issues/15#issuecomment-17345765
.


V Sreekanth | +91.9900.077.023 | [email protected]

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