The HA guidelines for deploying Hipchat call for using Redis Sentinel (https://confluence.atlassian.com/hipchatdc3/deployment-options-and-sizing-guidelines-for-hipchat-data-center-930911695.html). However, the configuration documentation says to "Use the default port 6379" (https://confluence.atlassian.com/hipchatdc3/configure-hipchat-data-center-nodes-909770912.html) and not use the Sentinel port of 26379.
When connecting HipChat to Sentinel, should port 26379 be used?
We don't support Redis Sentinel out of the box.
If this wasn't the case, you would need to tell Hipchat about all your Redis nodes and the Redis lib will do client-side load balancing.
The way to go is to deploy a Redis Sentinel cluster behind a load balancer like HAProxy.
We have a feature request open for this purpose as well:
HCPUB-3794 - Support Redis Sentinel
I hope this helps.
This helps a lot, thanks! Would you guys be willing to update the documentation with the requirement for fronting Redis with a proxy, at least until there is proper Sentinel support?
We found this out the hard way when the master node changed during maintenance and hipchat stopped working because it didn't make the switch to the new master.
- At least one additional Redis cache for failover, but ideally a total of three for a full HA Redis Sentinel cluster. See the official documentation here.
Earlier this year we made the difficult decision to discontinue our team messaging tools, Stride and Hipchat. The end of life date for Stride and Hipchat Cloud is quickly approaching - February 15, 2...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs