Glusterd2 Log flooded with error message from function registry.SearchByBrickPath() when one or brick is down

[rafikc30]

Observed behavior

Log flooding in glusterd2

Expected/desired behavior

Log file should not increase when a brick is down, as glusterfs designed to work as a highly available

Details on how to reproduce (minimal and precise)

1. Create a volume
2. mount the volume
3. Bring down a brick from the volume
4. Observe glusterd2 log

Information about the environment:

• Glusterd2 version used (e.g. v4.1.0 or master): master
• Operating system used: Fedora
• Glusterd2 compiled from sources, as a package (rpm/deb), or container: Source installed
• 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:

[atinmu]

Not a blocker for GCS/1.0 based on the revised MVP.