search

neshte / gluster-k8s-sidecar

Kubernetes sidecar for GlusterFS
MIT License
5 stars 3 forks source link

third node does not join gfs cluster #2

Closed rimusz closed 8 years ago

rimusz commented 8 years ago

tried to add a third gfs node to a healthy 2x nodes gfs cluster, the third node sidecar stuck on:

$ k logs gluster-3-oul4r gluster-sidecar -f
npm info it worked if it ends with ok
npm info using npm@3.9.3
npm info using node@v6.2.1
npm info lifecycle gluster-k8s-sidecar@0.1.0~prestart: gluster-k8s-sidecar@0.1.0
npm info lifecycle gluster-k8s-sidecar@0.1.0~start: gluster-k8s-sidecar@0.1.0

> gluster-k8s-sidecar@0.1.0 start /opt/neshte/gluster-k8s-sidecar
> forever src/index.js

warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
Starting up gluster-k8s-sidecar
rimusz commented 8 years ago

ah I see it has to be 4 peers gfs cluster

neshte commented 8 years ago

yes, multiples of your replication factor as said in the glusterfs documentation.

igoratencompass commented 7 years ago

If you set replication factor to 3 you can work with 3 nodes, right?

neshte commented 7 years ago

Nope, just multiples of replication factor, sorry