Backport: get gluster volume info from any gluster peer #414
Conversation
aesteve-rh
force-pushed
the
backport_get_gluster_fix
branch
from
b7d1952
to
0c98a14
Compare
There was a problem hiding this comment.
As for functionality, I trust the reviews from master.
The typos in code comments can be addressed in master but please separate the commit title from the rest by a blank line to prevent some git clients to present the whole commit message as a heading. And break the excessively long lines in the commit message.
The function _get_gluster_volinfo query the glusterfs volume info the the storage server, this is translated to the gluster client adding the parameter --remote-host which limits the query to one server, so we are converting the storage server as a single point of failure, if it is not available, it can led to cluster outtage. The proposed changed let the cluster cli to use any available gluster peer. Signed-off-by: José Enrique Gutiérrez Mazón <[email protected]> Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
force-pushed
the
backport_get_gluster_fix
branch
from
0c98a14
to
a63f8e7
Compare
I did not notice the issue with the commit message in the original patch... But at least we can fix it in the backport, true. Just pushed the change. Thanks for checking! |
The function _get_gluster_volinfo query the glusterfs volume info the the storage server, this is translated to the gluster client adding the parameter --remote-host which limits the query to one server, so we are converting the storage server as a single point of failure, if it is not available, it can led to cluster outtage. The proposed changed let the cluster cli to use any available gluster peer.
Bug-Url: https://bugzilla.redhat.com/2264175
Signed-off-by: José Enrique Gutiérrez Mazón [email protected]