We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@epsniff brought up a good point:
Could the Consumer have a Node() method?
via https://github.com/lytics/metafora/pull/79/files#r22186794
Right now the node name is an etcd-Coordinator specific concept. None of the core interfaces or Consumer have any name support.
Enforcing a cluster-unique name for each node/consumer seems like a generally good idea.
node string
metafora.Consumer
ConsumerConfig
<hostname>-<uuid>
Node() string
CoordinatorContext
BalancerContext
The text was updated successfully, but these errors were encountered:
No branches or pull requests
@epsniff brought up a good point:
via https://github.com/lytics/metafora/pull/79/files#r22186794
Right now the node name is an etcd-Coordinator specific concept. None of the core interfaces or Consumer have any name support.
Enforcing a cluster-unique name for each node/consumer seems like a generally good idea.
Possible Solution
node string
parameter tometafora.Consumer
- or switch to passing in a (new)ConsumerConfig
struct which would contain the node name.<hostname>-<uuid>
Node() string
method toCoordinatorContext
andBalancerContext
for them to use as they see fit.The text was updated successfully, but these errors were encountered: