-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Query DNS to automatically discover cluster peers #1108
Comments
I think there's an interesting sidebar discussion to be had about whether a node that is configured to use service discovery should surface the current status of that service discovery in e.g. the |
Closing in favour of #1337 (bam!) |
Suits me, I'd rather not have two things open for one thing here on GitHub because issues and PRs are functionally similar |
for the record...that's exactly what happened here. #1337 didn't get merged, and if this stayed closed, we'd have lost the enhancement request entirely. (Which may still happen, given this is nearly 18 months old with no action.) |
We can streamline cluster setup by querying DNS for an SRV record containing the hostnames of other cluster members. Service records are defined in RFC 2782 for this purpose but this is not a strictly academic exercise. As a practical example Kubernetes will create SRV records for members of a StatefulSet. I created a sidecar container that uses those SRV records to automatically join up the members of a StatefulSet here:
https://github.com/kocolosk/couchdb-statefulset-assembler
I think it would be interesting to push that logic down into mem3 directly. I'm envisioning a system that can be configured like so
If a user omits the
service_record_name
CouchDB would attempt to generate the appropriate record for the query by prepending_couchdb._tcp.
to the DNS domain name portion of the host / VM / container FQDN.The text was updated successfully, but these errors were encountered: