Open Shrivaibavi opened 5 years ago
Can you paste brick logs of the time when you started volume "xyz" ?
@rishubhjain The logs are quite big. you can use my machine instead if you want to debug. 10.70.35.30
Two fix required.
1) glustercli - Blindly catching "Connection Refused" error and displaying as glusterd2 is probably down. https://github.com/gluster/glusterd2/blob/master/glustercli/cmd/common.go#L43 2) In all Brick ops, handle connection refused error and act accordingly. For example, while stopping the brick glusterd2 tries to connect and send brickop to stop, Ignore if connection refused error.
@harigowtham What's the update on this?
Unable to reproduce the issue. will try it a few more times. There is one odd error message "no such file or directory" is the error message at one of the node. Need to see deeper as to why this one is different.
@harigowtham try to stop the volume immediately after glusterd2 restart(Before bricks connect back to glusterd2)
Observed behavior
Expected/desired behavior
The volume stop should be successful
Details on how to reproduce (minimal and precise)
Information about the environment:
Glusterd2 version used (e.g. v4.1.0 or master): glusterd version: v6.0-dev.88.gitea22407 git SHA: ea22407 go version: go1.11.2 go OS/arch: linux/amd64
Operating system used:
Glusterd2 compiled from sources, as a package (rpm/deb), or container:
Using External ETCD: (yes/no, if yes ETCD version):
If container, which container image:
Using kubernetes, openshift, or direct install:
If kubernetes/openshift, is gluster running inside kubernetes/openshift or outside:
Other useful information
[root@dhcp35-30 ~]# cat /etc/glusterd2/glusterd2.toml
localstatedir = "/var/lib/glusterd2" logdir = "/var/log/glusterd2" logfile = "glusterd2.log" loglevel = "INFO" rundir = "/var/run/glusterd2" defaultpeerport = "24008" peeraddress = ":24008" clientaddress = ":24007" restauth = false etcdendpoints = "http://10.70.35.173:2379" noembed = true
brick logs
uuid.toml
from all nodes (default /var/lib/glusterd2/uuid.toml)statedump
from any one of the nodeUseful commands