-
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
Running maxwell on kubernetes #2036
Comments
Honestly I think that running maxwell on kubernetes PLUS raft feels overkill -- k8s already has a great mechanism for running one and only one copy of a service like maxwell at time, plus has support for restarting it when it's down, or when a node dies, etc. If you decide you really really need to do that i think you have to configure jgroups-raft to talk via TCP instead of its normal multicast thing but it's out of my expertise; I'd check over there. |
I am having same issue
each pod is creating its own cluster its working in k8s
Also, faced an issue with TCPPING https://issues.redhat.com/browse/AS7-4828 https://bugzilla.redhat.com/show_bug.cgi?id=900707
in case I have RAFT configured with port enabled:
k8s config
|
guys, you really don't need k8s + raft. There's really no need; let k8s run "1 and exactly 1" copy of maxwell ; if one dies k8s will replace it. |
I want running maxwell on kubernets.
Below is my
raft.xml
file:Below is my kubernetes deploy yaml file:
maxwell.yaml
Content of the
maxwell.sh
script in the yaml file:When i execute command:
kubectl apply -f maxwell.yaml
, The logs for the three Pods are as follows:What should I do to get the three nodes to start an election?
The text was updated successfully, but these errors were encountered: