-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Redis onpremise high available #744
Comments
There are 2 options here with the latest stable Windows release: 3.0.504
Each of these have pros and cons. There's a great Stack Overflow answer on the benefits and downsides of each approach here: https://stackoverflow.com/q/31143072/13249 |
For sentinel, it seems as per post. We need to have odd number so i guess we need atlest 5 nodes.
Client will connect to which sentinel nodes ? |
So, does StackExchange.Redis work with Sentinel? The issue #692 suggests that it was not yet merged. |
we're aware of the patch, and we intend testing it in our short term plans
- historically we just haven't been in a place to have enough sentinel
knowledge to properly assess it, but we're looking to change that
On 19 Dec 2017 8:22 p.m., "ratzinho87" <notifications@github.com> wrote:
So, does StackExchange.Redis work with Sentinel? The issue #692
<#692> suggests
that it was not yet merged.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#744 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABDsOiwLo1IVC9QnjPGxi6LNb1t0MAeks5tCBsOgaJpZM4QpSv7>
.
|
Discussion happening in #692 (which still lacks unit tests at the moment). I'm going to take another crack at trying to get the test suite green on Appveyor to assist this along. Closing this particular issue out to cleanup, since asked and answered :) |
Hi,
How to run redis onpremise windows 2016 in HA configuration?
We want to avoid SPoC of redis instance
Redis sentient is not available for windows it seems.
Thanks
The text was updated successfully, but these errors were encountered: