Commands to get healed entries & entries on which heal failed information for the volumes in gd2

[Shrivaibavi]

Observed behavior

The command to get healed entries information for the volume by executing:
'gluster volume heal info healed'

The command to get entries on which heal failed for the volume by executing:
'gluster volume heal info heal-failed'

I see these commands in gd1 whereas missing in gd2.

Expected/desired behavior

Details on how to reproduce (minimal and precise)

Information about the environment:

• Glusterd2 version used (e.g. v4.1.0 or master):
• 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

• glusterd2 config files from all nodes (default /etc/glusterd2/glusterd2.toml)
• glusterd2 log files from all nodes (default /var/log/glusterd2/glusterd2.log)
• ETCD configuration
• Contents of uuid.toml from all nodes (default /var/lib/glusterd2/uuid.toml)
• Output of statedump from any one of the node

Useful commands

• To get glusterd2 version

  glusterd2 --version
  

• To get ETCD version

  etcd --version
  

• To get output of statedump

  curl http://glusterd2-IP:glusterd2-Port/statedump
  

[Shrivaibavi]

@vpandey-RH @aravindavk @atinmu

[vpandey-RH]

@Shrivaibavi I have a few Questions :

1- Do we need to provide volume name as well in the above two commands ?
2- I tried to run the command in GD1 setup but the output showed that the command doesn't exist. Do you have updated GD1 ?