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
Good evening. Can you help me. I'm using libcluster in Kubernetes with the strategy Cluster.Strategy.Kubernetes and libring for dynamic messaging
config :libcluster, topologies: [ feed: [ strategy: Cluster.Strategy.Kubernetes, config: [kubernetes_selector: "app=feed", kubernetes_node_basename: "feed"] ], fixture: [ strategy: Cluster.Strategy.Kubernetes, config: [kubernetes_selector: "app=fixture", kubernetes_node_basename: "fixture"] ], web: [ strategy: Cluster.Strategy.Kubernetes, config: [kubernetes_selector: "app=web", kubernetes_node_basename: "web"] ] ]
For some reason, sometimes after node moved to Terminating state, it still in cluster. Eventually, request to such node results in request timeout.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Good evening. Can you help me. I'm using libcluster in Kubernetes with the strategy Cluster.Strategy.Kubernetes and libring for dynamic messaging
For some reason, sometimes after node moved to Terminating state, it still in cluster. Eventually, request to such node results in request timeout.
The text was updated successfully, but these errors were encountered: