Open xiaosuiba opened 7 years ago
We'll look into that and make the cluster domain configurable in the container.
Our peer-finder does not have this implemented yet. We have to compile it again and put it in the image. As i can see this should not cause any issues.
I'm also having an issue with it getting stuck; I rebuild the container using a newer version of peer-finder and it's also in an infinate loop. However we're not using custom dns.
2017/09/06 16:52:33 Have not found myself in list yet.
My Hostname: mariadb-cluster-1.mariadb-cluster.amze-drupal-example-mariadb-cluster.svc.cluster.local
Hosts in list: a59b90d7.mariadb-cluster.amze-drupal-example-mariadb-cluster.svc.cluster.local
2017/09/06 16:52:34 Have not found myself in list yet.
My Hostname: mariadb-cluster-1.mariadb-cluster.amze-drupal-example-mariadb-cluster.svc.cluster.local
Hosts in list: a59b90d7.mariadb-cluster.amze-drupal-example-mariadb-cluster.svc.cluster.local
and so on.
@rtprio What you're experiencing seems to be a mismatch between what peer-finder looks for (mariadb-cluster-1) and what the service reports (a59b90d7). This could be different issue related to the service.
I also have the same output as @rtprio with another service. I really don't understand what I'm doning wrong. The dns is not changed, I'm using the OpenShift one.
That means that peer-finder is broken ? should I try another version, and wich one ?
@tongpu I tried to use that peer-finder bin: https://github.com/adfinis-sygroup/openshift-mariadb-galera/blob/master/k8s-mariadb-galera-centos/root/usr/bin/peer-finder
And now, the problem disapeared, sorry for my comment, that was the bad repository. I sould create an issue on kubernetes/contrib instead.
Hi, I was deploying this statefulset on my local kubernetes(v1.5) cluster using the script
galera_k8s_v1.5.yml
. But the first pod failed to start. After checking the log serveral times I found it stuck at:I was pretty sure the dns is working perfectly, so I checked the source code of peer-finder and did some debugging. Then I found out where the problem is. https://github.com/kubernetes/contrib/blob/master/pets/peer-finder/peer-finder.go#L43
peer-finder is asking for a domain flag which could be passed by
--domain
, or it'll use the default settingcluster.local
. In my case, I used a custom dns domaintest.local
instead of the default onecluster.local
. Then peer-finder will comparemysql-0.galera.default.svc.cluster.local
withmysql-0.galera.default.svc.test.local
and then stuck in a infinite loop. So could anyone add an ENV or something else and pass it to the peer-finder to get it work?