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

REDIS_ADDR should always be used for master/slave connections #26

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jhitt25
Copy link

@jhitt25 jhitt25 commented Jan 23, 2019

ANNOUNCE_ADDR should be used as the address consul reports to clients.
REDIS_ADDR should always be used internally for SLAVEOF operations.

ANNOUNCE_ADDR should be used as the address consul reports to clients.
REDIS_ADDR should always be used internally for SLAVEOF operations.
@jhitt25
Copy link
Author

jhitt25 commented Jan 23, 2019

We use stunnel to encrypt our redis server-to-server connections. We want to make a standard address publicly accessible, but redis itself must communicate over a localhost address. Using ANNOUNCE_ADDR as the master address handily breaks this setup.

This setup will use REDIS_ADDR in the service ID, while still using ANNOUNCE_ADDR for the service address and port.

@jippi
Copy link
Contributor

jippi commented Jan 24, 2019

I need to review this carefully later, probably won't be for a couple of weeks due to work priorities.

It would be great to have teats to support the changes to avoid regressions :)

@jhitt25
Copy link
Author

jhitt25 commented Jan 25, 2019

Agreed. I'm not a Go developer by trade, but i'll see what i can glean from the project setup. :)
I'll be out for a few weeks myself, but i figured it was worth getting a patch started.

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

Successfully merging this pull request may close these issues.

2 participants