Skip to content

Conversation

@jolynch
Copy link
Collaborator

@jolynch jolynch commented Oct 16, 2015

This option can be used to enable custom server level options in the
fronting haproxy instances, which allows things like declaring that a
particular node is a backup or should be healthchecked a special way.

Synapse already partially supports this option and it will have full support once airbnb/synapse#144 is merged.

This option can be used to enable custom server level options in the
fronting haproxy instances, which allows things like declaring that a
particular node is a backup or should be healthchecked a special way.
@Jaykah
Copy link

Jaykah commented Nov 24, 2015

I can confirm this is passing options to Zookeper successfully. One note though - if the config is changed to include those additional options and then a Nerve restart is done, a new node is created in Zookeeper, but the old ephemeral node does not disappear until manually removed.

@jolynch
Copy link
Collaborator Author

jolynch commented Nov 25, 2015

@Jaykah I'm going to merge this because I can't reproduce that bug. Which version of ruby, nerve, and zookeeper are you using? Are you sure that the old nerve process is no longer running?

@zhitaoli I can merge this now but I can't really get it into production to verify for at least a week (thanksgiving).

jolynch added a commit that referenced this pull request Nov 25, 2015
Thread haproxy_server_options through from reporters
@jolynch jolynch merged commit 8c86441 into master Nov 25, 2015
@zhitaoli
Copy link

@jolynch Awesome! Many thanks for the progress!

@panchr panchr deleted the support_haproxy_server_options branch March 19, 2020 20:03
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.

4 participants