[Bugs] [Bug 1162095] gstatus: gstatus fails if the glusterd on local machine is not running.

bugzilla at redhat.com bugzilla at redhat.com
Thu Nov 13 06:21:11 UTC 2014


https://bugzilla.redhat.com/show_bug.cgi?id=1162095



--- Comment #4 from Paul Cuzner <pcuzner at redhat.com> ---
Yep - that could work. Everything gstatus does is through the CLI and where
available interpreting the XML output. When gstatus starts up it creates some
node objects, so there is a potential of pushing the CLI interaction to a
separate class based on one of the nodes that have been detected (I was going
to do this anyway, since I want to add a CLI timeout)

A quick check shows that all but one of the commands used in gstatus would work
with a --remote-host...here's the 'problem child'

[root at rhs3-2 ~]# gluster --remote-host=rhs3-1 vol heal admin info 
admin: Not able to fetch volfile from glusterd
Volume heal failed

By default I don't run the heal command since it's slow, so if the user
requests the heal data and the local node is down gstatus could just terminate
early with an error that says that data isn't available since the local
glusterd is down..

Thoughts?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=YNs6xMyKhe&a=cc_unsubscribe


More information about the Bugs mailing list