This repository was archived by the owner on Mar 26, 2020. It is now read-only.
Volume status shows PID as 0 for few volumes #1487
Description
Observed behavior
Volume status shows PID as 0 for few volumes.
Expected/desired behavior
Brick process should be running on that brick and volume status should show the PID of the brick process.
Details on how to reproduce (minimal and precise)
- Create a 3 node GCS setup using vagrant.
- Create 500 PVCs.
- Check glustercli volume status
Information about the environment:
- Glusterd2 version used (e.g. v4.1.0 or master): v6.0-dev.114.gitd51f60b
- Operating system used: Centos 7.6
- Glusterd2 compiled from sources, as a package (rpm/deb), or container:
- Using External ETCD: (yes/no, if yes ETCD version): yes
- If container, which container image:
- Using kubernetes, openshift, or direct install:
- If kubernetes/openshift, is gluster running inside kubernetes/openshift or outside: kubernetes
glusterd2 statedump:
statedump_new_2.txt