-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Second redis service is redundant #73
Comments
I saw something like this at There are twice Redis instance, I thing, Worker never discover a second Redis instance. May be, Redis shoud be configured as node of Redis if is possible. Another thing is about Redis host name, the Vote App and Worker Services connect at redis host name. If at cluster have twice Redis instance, Vote every time connect to what Redis instance? Some times when I vote, the vote is not computed, I guess, my vote was at another Redis which is not connected by Worker Services. What you think about that @zavermax ? |
If I understand the .NET worker correctly, it tries to reconnect on failure. So a changed ip address might be compensated. The Java worker doesn't seem to be resilient on connection errors, yet. The fact that a worker can only connect to a single Redis instance indeed arises problems when votes go to the "other" instance. The worker just won't see any votes. I see several options here:
|
@gesellix At my demo enviroment I reduce the Redis replicas to a single instance and all work fine. But, I guess the better solution is implement a Redis Cluster like you told us. Another bad thing I see at .NET worker is that I think change Redis for a RabbitMQ. |
Fixed |
There are two redis services and one worker service. Worker service would start, resolve redis host name to an ip and use this ip until stopped. Second redis service is never going to be talked to.
The text was updated successfully, but these errors were encountered: