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

Adding ability to specify bind address for NATS address #69

Merged
merged 7 commits into from
Jul 26, 2023

Conversation

maxpert
Copy link
Owner

@maxpert maxpert commented Jul 25, 2023

Reducing down changes to only specify bind address.

Old given that Marmot can now boot embedded NATS with dns://<DNS_ENTRIES:<port>/ to effective nats://<resolved_ip>:<port> for multiple entries, and actually wait for minimum number of nodes to come up before it proceeds, it was very obvious next step to automatically add/remove these entries from NATs server in background. This PR lays down foundation to do that in a dynamic way, so that cluster membership can be elastic based on DNS discovery.

NOTE Turns out the NATS configuration can't be reloaded in disk persistent mode which is core requirement for Marmot flows. In order to keep the good parts I am using this PR to strip extra stuff off and only keep couple of things I fixed while fixing PR.

@maxpert maxpert changed the title Adding capability to automatically reload DNS entries into embedded NATS Adding ability to specify bind address for NATS address Jul 26, 2023
@maxpert maxpert merged commit ceea34f into master Jul 26, 2023
9 checks passed
@maxpert maxpert deleted the auto-reload-dns branch July 26, 2023 14: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.

None yet

1 participant