-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add Sentinel Master units ip to the app databag #95
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-5200.
|
Hello @alithethird thanks for creating this request. Just for clarification: You need the Redis Sentinel leader information, not the |
Hi @reneradoi. Thanks for the answer. Sorry I am not very familiar with and thought they were the same. I need the one that has write access to the database. That is the Sentinel leader I guess? |
Yes @alithethird that would be the Sentinel leader. |
Thanks for clarifying that. I will update the issue accordingly. |
This is also impacting the Commercial Systems team deployment of Superset. Commenting here for visibility. I see there is a PR to resolve so will monitor that. |
New version has been released as revision 35 to Charmhub. |
Thanks a lot! |
Closing the issue as this has been provided with #96. |
When multiple units of
Redis
is deployed the units put their ip into the unit databag and consumer charms can not find which unit is the leader. An example bug is here: canonical/discourse-k8s-operator#268This also fixes the issue where after a reboot the consumer charm doesn't refresh the redis ip. Ip refreshes in the unit databag but the charm doesn't read that because its cashed. An example bug is here: https://bugs.launchpad.net/juju/+bug/2063087
Adding the Sentinel Master units ip to the app databag would fix both of these bugs.
The text was updated successfully, but these errors were encountered: